Methods and apparatus for dynamic control of connections to co-existing radio access networks

ABSTRACT

Methods and apparatus for monitoring and controlling access to coexisting first and second networks within a venue. In one embodiment, the first network is a managed content delivery network that includes one or more wireless access points (APs) in data communication with a backend controller which communicates with a dedicated background scanner. The background scanner scans for coexisting networks within the venue, and reports this to the controller. In one variant, the controller dynamically adjusts transmit characteristics of the AP(s) to manage interference between the coexisting networks. In another variant, the controller causes the energy detect threshold of a client device to be lowered so that the device may detect WLAN signals in a scenario where a coexisting RAT (for example, LTE-U or LTE-LAA) occupies the same channel and/or frequency.

PRIORITY

This application is a divisional of and claims the benefit of priorityto U.S. patent application Ser. No. 15/615,686 of the same title filedJun. 6, 2017, issuing as U.S. Pat. No. 10,638,361 on Apr. 28, 2020,which is incorporated herein by reference in its entirety.

RELATED APPLICATIONS

The present application is generally related to the subject matter ofco-owned and co-pending U.S. patent application Ser. No. 15/612,630filed Jun. 2, 2017 and entitled “APPARATUS AND METHODS FOR PROVIDINGWIRELESS SERVICE IN A VENUE”; U.S. patent application Ser. No.15/183,159 filed Jun. 15, 2016 and entitled “APPARATUS AND METHODS FORMONITORING AND DIAGNOSING A WIRELESS NETWORK”; U.S. patent applicationSer. No. 15/063,314 filed Mar. 7, 2016 and entitled “APPARATUS ANDMETHODS FOR DYNAMIC OPEN-ACCESS NETWORKS”; U.S. patent application Ser.No. 15/002,232 filed Jan. 20, 2016 and entitled “APPARATUS AND METHODFOR WIRELESS NETWORK SERVICES IN MOVING VEHICLES”; U.S. patentapplication Ser. No. 14/959,948 filed Dec. 4, 2015 and entitled“APPARATUS AND METHOD FOR WIRELESS NETWORK EXTENSIBILITY ANDENHANCEMENT”; and U.S. patent application Ser. No. 14/959,885 filed Dec.4, 2015 and entitled “APPARATUS AND METHODS FOR SELECTIVE DATA NETWORKACCESS”, each of the foregoing incorporated herein by reference in itsentirety.

COPYRIGHT

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever.

BACKGROUND 1. Technological Field

The present disclosure relates generally to the field of wirelessnetworks and specifically, in one or more exemplary embodiments, tomethods and apparatus for dynamically controlling and optimizingconnections to coexisting radio access networks (“RANs”), such as thoseproviding connectivity via Wi-Fi, LTE-U (Long Term Evolution inunlicensed spectrum) and/or LTE-LAA (Long Term Evolution, LicensedAssisted Access) technologies.

2. Description of Related Technology

A multitude of wireless networking technologies, also known as RadioAccess Technologies (“RATs”), provide the underlying means of connectionfor radio-based communication networks to user devices. User clientdevices currently in use (e.g., smartphone, tablet, phablet, laptop,smartwatch, or other wireless-enabled devices, mobile or otherwise)generally support one or more RATs that enable the devices to connect toone another, or to networks (e.g., the Internet, intranets, orextranets). In particular, wireless access to other networks by clientdevices is made possible by wireless technologies that utilize networkedhardware, such as a wireless access point (“WAP” or “AP”), small cells,femtocells, or cellular towers, serviced by a backend or backhaulportion of service provider network (e.g., a cable network). A user maygenerally access the network at a “hotspot,” a physical location atwhich the user may obtain access by connecting to modems, routers, APs,etc. that are within wireless range.

One such technology that enables a user to engage in wirelesscommunication (e.g., via services provided through the cable networkoperator) is Wi-Fi® (IEEE Std. 802.11), which has become a ubiquitouslyaccepted standard for wireless networking in consumer electronics. Wi-Fiallows client devices to gain convenient high-speed access to networks(e.g., wireless local area networks (WLANs)) via one or more accesspoints.

Commercially, Wi-Fi is able to provide services to a group of userswithin a venue or premises such as within a trusted home or businessenvironment, or outside, e.g., cafes, hotels, business centers,restaurants, and other public areas. A typical Wi-Fi network setup mayinclude the user's client device in wireless communication with an AP(and/or a modem connected to the AP) that are in communication with thebackend, where the client device must be within a certain range thatallows the client device to detect the signal from the AP and conductcommunication with the AP.

Another wireless technology in widespread use is Long-Term Evolutionstandard (also colloquially referred to as “LTE,” “4G,” “LTE Advanced,”among others). An LTE network is powered by an Evolved Packet Core(“EPC”), an Internet Protocol (IP)-based network architecture andeNodeB—Evolved NodeB or E-UTRAN node which part of the Radio AccessNetwork (RAN), capable of providing high-speed wireless datacommunication services to many wireless-enabled devices of users with awide coverage area.

Currently, most consumer devices include multi-RAT capability; e.g.; thecapability to access multiple different RATs, whether simultaneously, orin a “fail over” manner (such as via a wireless connection managerprocess running on the device). For example, a smartphone may be enabledfor LTE data access, but when unavailable, utilize one or more Wi-Fitechnologies (e.g., 802.11g/n/ac) for data communications.

The capabilities of different RATs (such as LTE and Wi-Fi) can be verydifferent, including regarding establishment of wireless service to agiven client device. For example, there is a disparity between thesignal strength threshold for initializing a connection via Wi-Fi vs.LTE (including LTE-U and LTE-LAA). As a brief aside, LTE-U enables datacommunication via LTE in an unlicensed spectrum (e.g., 5 GHz) to provideadditional radio spectrum for data transmission (e.g., to compensate foroverflow traffic). LTE-LAA uses carrier aggregation to combine LTE inunlicensed spectrum (e.g., 5 GHz) with the licensed band.

Typical levels of signal strength required for LTE-U or LTE-LAA serviceare approximately −80 to −84 dBm. In comparison, Wi-Fi can be detectedby a client device based on a signal strength of approximately −72 to−80 dBm, i.e., a higher (i.e., less sensitive) detection threshold.Moreover, the mechanisms for connecting to various types of RATs mayvary in their protocol, including what is colloquially referred to as“politeness.” For instance, a Wi-Fi connection protocol may bestructured to be unobtrusive when in the presence of other RATs suchthat the other RATs will preferentially connect before Wi-Fi. This isparticularly true where the RF signal strength levels for the variousRATs are generally of similar magnitude (i.e., such that no particularRAT “stands out”).

When a client device is in an environment where coexisting LTE and Wi-Fiservices are available for connection to a network (e.g., publicvenues), the client device may automatically and/or persistentlyprioritize a connection to LTE providers despite the presence of nearbyexisting Wi-Fi equipment (e.g., an AP providing network connectivity viaWi-Fi). Specifically, if LTE and Wi-Fi services are available on thesame operating frequency band (e.g., 5 GHz), the client device mayconnect via LTE by virtue of its relatively aggressive connectionmechanism, even when it is not the intention of the user. For instance,the user may be under a service contract with one or more LTE carriersthat may charge access fees or count LTE “data” consumption against alimited quota, and hence desire to use Wi-Fi (and its correspondingunlimited data) when at all possible. Other instances where Wi-Fi isrequired or heavily preferred may include, inter alia, (i) forconservation of battery power at low reserves, (ii) when consuming dataservices over a comparatively long period of time (e.g., voice-over-IP(VoIP) calls, video chats, or large data transfers), and/or (iii) foraccess to services particular to a service provider of which the user isa subscriber (including for use of a software application specificallydesigned for use by the service provider). The user may also prefer aconsistent connection to avoid discontinuities associated with handoversbetween LTE nodes (cell towers, small cells, eNBs (evolved NodeBs), basestations, etc.). Moreover, when LTE or other RAT connectivity isprioritized by the user's mobile devices, some service providers (e.g.,cable network operators) cannot provide services to their existingsubscribers or capture new ad hoc users as effectively within publicvenues as compared to use of Wi-Fi.

Therefore, solutions are needed to, inter alia, allow Wi-Fi or otherWLAN RAT service providers to compete effectively against LTE or othermore “aggressive” RATs in such coexistence environments. Specifically,what are needed are means for dynamically controlling access toco-existing RATs such that user and/or service provider preferences andfunctionality are optimized.

SUMMARY

The present disclosure addresses the foregoing needs by providing, interalia, methods and apparatus for dynamically controlling connections tocoexisting radio access networks, including the implementation ofsituation- and/or location-specific connection rules.

In one aspect of the present disclosure, a method for enabling wirelessconnectivity to at least one client device is provided. In oneembodiment, the method includes: detecting a first type of wirelesssignal, the detecting comprising receiving data from a first radiofrequency (RF) receiver apparatus; modifying one or more parametersassociated with an interface apparatus utilizing a second type ofwireless signal and based at least in part on the data from the first RFreceiver apparatus; and transmitting data relating to the modified oneor more parameters to the interface apparatus, the transmitted dataenabling the interface apparatus to adjust one or more operationalcharacteristics thereof with respect to the second type of wirelesssignal.

In another aspect of the present disclosure, a controller apparatus isprovided. In one embodiment, the controller apparatus is configured foruse within a managed content delivery network, and to manage wirelessconnectivity to a wireless-enabled device, and includes: a processorapparatus; and a storage apparatus in data communication with theprocessor apparatus and having a non-transitory computer-readablestorage medium, the storage medium comprising at least one computerprogram having a plurality of instructions stored thereon. In onevariant, the plurality of instructions are configured to, when executedby the processor apparatus, cause the controller apparatus to: detect aconcurrent deployment of a first radio protocol and a second radioprotocol within at least a prescribed area, the detection being based atleast on data received from a first downstream network apparatus; obtaindata representative of a configuration of an wireless access point (AP)located within the prescribed area, the data comprising data descriptiveof a plurality of parameters associated with a wireless interface of thewireless AP utilizing the first radio protocol; modify the datarepresentative of the configuration, the modification comprising anupdate of at least one of the plurality of parameters; and transmit themodified data representative of the configuration to the wireless AP,the modified data enabling the wireless AP to modify at least oneoperational characteristic associated with the wireless interface basedon the updated at least one parameter.

In a further aspect of the present disclosure, a non-transitorycomputer-readable storage medium is provided.

In a further aspect, a networked system configured to provide wirelessLAN (WLAN) connectivity to at least one wireless-enabled device locatedwithin a venue is disclosed. In one embodiment, the system includes:scan apparatus configured to detect at least first radio frequency (RF)signals associated with a first type of wireless technology; andconfigure data for transmission to a wireless contention managementprocess, the data comprising information related to the at least firstRF signals; and a controller apparatus in network data communicationwith the scan apparatus, the controller apparatus comprising thewireless contention management process and configured to: receive theconfigured data and provide the received configured data to thecontention management process; access configuration data relating to atleast one wireless access point (AP) within the WLAN; utilize thecontention management process to modify the accessed configuration datacontained based at least on the configured data; transmit the modifiedconfiguration data to the at least one wireless access point; and causethe at least one wireless access point to adjust at least oneconnectivity parameter associated with a WLAN interface of the at leastone access point based on the modified configuration data received fromthe controller apparatus.

In yet another aspect, a method of preferentially causing wireless LAN(WLAN) access for a multi-mode mobile client device is disclosed. In oneembodiment, the client device has both a WLAN interface and a cellulardata interface, and a connection management process configured to selectone of the WLAN interface and the cellular data interface, and themethod includes: wirelessly receiving data at the client device, thereceived data configured to enable the client device to adjust one ormore parameters associated with the WLAN interface, the adjustment tocompensate for detection of operation of non-WLAN radio accesstechnology within an area within which the client device is currentlylocated; determining, using at least the connection management process,that the cellular data interface is operating at a level of performancegreater than that of the WLAN interface; based at least on thedetermining, adjusting the one or more parameters associated with theWLAN interface based at least on the received data; thereafterevaluating, using at least the connection management process, at leastone aspect of the performance of the WLAN interface: and based at leaston the evaluating, selecting the WLAN interface for data communications.

In another aspect, methods of characterizing one or more RATinterference sources is disclosed. In one embodiment, thecharacterization comprises detection and decoding of one or morebroadcast channels associated with the one or more RATs, and calculatingRF-related properties based on the decoded signals and knowledge of pathloss data for the channels.

In a further aspect of the present disclosure, business methods forenabling an alternative type of wireless connectivity to one or moreuser devices are provided.

In a further aspect of the present disclosure, business methods forcollecting data usage information via wireless connectivity provided toone or more user devices are provided.

These and other aspects shall become apparent when considered in lightof the disclosure provided herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram illustrating an exemplary hybridfiber network configuration useful with various aspects of the presentdisclosure.

FIG. 1a is a functional block diagram illustrating one exemplary networkheadend configuration useful with various aspects of the presentdisclosure.

FIG. 1b is a functional block diagram illustrating one exemplary localservice node configuration useful with various aspects of the presentdisclosure.

FIG. 1c is a functional block diagram illustrating one exemplarybroadcast switched architecture (BSA) network useful with variousaspects of the present disclosure.

FIG. 1d is a functional block diagram illustrating one exemplarypacketized content delivery network architecture useful with variousaspects of the present disclosure.

FIG. 2 is a functional block diagram of an exemplary embodiment of awireless network infrastructure useful with various embodiments of thepresent disclosure.

FIG. 2a is a functional block diagram of an exemplary embodiment of theinfrastructure of FIG. 2, in the context of cable network architectureproviding WLAN services to a customer premises such as an enterprise orvenue.

FIG. 3 is a graphical representation of a typical implementation of aprior art Wi-Fi back-off mechanism.

FIG. 3a is a graphical representation of a typical prior art networkscenario in which only Wi-Fi connectivity is available.

FIG. 3b is a graphical representation of a typical prior art coexistencescenario in which Wi-Fi connectivity and LTE-U or LTE-LAA connectivityare available.

FIG. 4 is a high-level graphical representation of the operation of theexemplary network architecture of FIG. 2, in which the Wi-Fi connectionis controlled within a venue or environment deploying coexisting Wi-Fiand LTE-U or LTE-LAA services.

FIG. 5 is logical flow diagram of an exemplary generalized method forenabling connectivity via a wireless signal to at least one clientdevice in a coexistence environment according to the present disclosure.

FIG. 5a is logical flow diagram of an exemplary implementation of thegeneralized method for enabling connectivity of FIG. 5.

FIG. 5b is logical flow diagram of another exemplary implementation ofthe generalized method for enabling connectivity of FIG. 5.

FIG. 6 is a ladder diagram illustrating an exemplary communication flowfor configuring new Wi-Fi connectivity settings with an exemplaryCoexistence Controller (CC) in accordance with one embodiment of themethod of FIG. 5.

FIG. 7 is a functional block diagram illustrating an exemplarycoexistence controller (CC) apparatus useful with various embodiments ofthe present disclosure.

FIG. 8 is a functional block diagram illustrating an exemplarybackground radio scanner useful with various embodiments of the presentdisclosure

All figures © Copyright 2017 Time Warner Cable Enterprises, LLC. Allrights reserved.

DETAILED DESCRIPTION

Reference is now made to the drawings wherein like numerals refer tolike parts throughout.

As used herein, the term “access point” refers generally and withoutlimitation to a network node which enables communication between a useror client device and another entity within a network, such as forexample a Wi-Fi AP, or a Wi-Fi-Direct enabled client or other deviceacting as a Group Owner (GO).

As used herein, the term “application” (or “app”) refers generally andwithout limitation to a unit of executable software that implements acertain functionality or theme. The themes of applications vary broadlyacross any number of disciplines and functions (such as on-demandcontent management, e-commerce transactions, brokerage transactions,home entertainment, calculator etc.), and one application may have morethan one theme. The unit of executable software generally runs in apredetermined environment; for example, the unit could include adownloadable Java Xlet™ that runs within the JavaTV™ environment.

As used herein, the terms “client device” or “user device” include, butare not limited to, set-top boxes (e.g., DSTBs), gateways, modems,personal computers (PCs), and minicomputers, whether desktop, laptop, orotherwise, and mobile devices such as handheld computers, PDAs, personalmedia devices (PMDs), tablets, “phablets”, smartphones, and vehicleinfotainment systems or portions thereof.

As used herein, the term “codec” refers to a video, audio, or other datacoding and/or decoding algorithm, process or apparatus including,without limitation, those of the MPEG (e.g., MPEG-1, MPEG-2,MPEG-4/H.264, H.265, etc.), Real (RealVideo, etc.), AC-3 (audio), DiVX,XViD/ViDX, Windows Media Video (e.g., WMV 7, 8, 9, 10, or 11), ATI Videocodec, or VC-1 (SMPTE standard 421M) families.

As used herein, the term “computer program” or “software” is meant toinclude any sequence or human or machine cognizable steps which performa function. Such program may be rendered in virtually any programminglanguage or environment including, for example, C/C++, Fortran, COBOL,PASCAL, assembly language, markup languages (e.g., HTML, SGML, XML,VoXML), and the like, as well as object-oriented environments such asthe Common Object Request Broker Architecture (CORBA), Java™ (includingJ2ME, Java Beans, etc.) and the like.

As used herein, the term “DOCSIS” refers to any of the existing orplanned variants of the Data Over Cable Services InterfaceSpecification, including for example DOCSIS versions 1.0, 1.1, 2.0, 3.0and 3.1.

As used herein, the term “headend” or “backend” refers generally to anetworked system controlled by an operator (e.g., an MSO) thatdistributes programming to MSO clientele using client devices. Suchprogramming may include literally any information source/receiverincluding, inter alia, free-to-air TV channels, pay TV channels,interactive TV, over-the-top services, streaming services, and theInternet. As used herein, the terms “Internet” and “internet” are usedinterchangeably to refer to inter-networks including, withoutlimitation, the Internet. Other common examples include but are notlimited to: a network of external servers, “cloud” entities (such asmemory or storage not local to a device, storage generally accessible atany time via a network connection, and the like), service nodes, accesspoints, controller devices, client devices, etc.

As used herein, the term “LTE” refers to, without limitation and asapplicable, any of the variants of the Long-Term Evolution wirelesscommunication standard, including LTE-U (Long Term Evolution inunlicensed spectrum), LTE-LAA (Long Term Evolution, Licensed AssistedAccess), LTE-A (LTE Advanced), 4G LTE, WiMAX, and other wireless datastandards, including GSM, UMTS, CDMA2000, etc. (as applicable).

As used herein, the term “memory” includes any type of integratedcircuit or other storage device adapted for storing digital dataincluding, without limitation, ROM, PROM, EEPROM, DRAM, SDRAM, DDR/2SDRAM, EDO/FPMS, RLDRAM, SRAM, “flash” memory (e.g., NAND/NOR), 3Dmemory, and PSRAM.

As used herein, the terms “microprocessor” and “processor” or “digitalprocessor” are meant generally to include all types of digitalprocessing devices including, without limitation, digital signalprocessors (DSPs), reduced instruction set computers (RISC),general-purpose (CISC) processors, microprocessors, gate arrays (e.g.,FPGAs), PLDs, reconfigurable computer fabrics (RCFs), array processors,secure microprocessors, and application-specific integrated circuits(ASICs). Such digital processors may be contained on a single unitary ICdie, or distributed across multiple components.

As used herein, the terms “MSO” or “multiple systems operator” refer toa cable, satellite, or terrestrial network provider havinginfrastructure required to deliver services including programming anddata over those mediums.

As used herein, the terms “network” and “bearer network” refer generallyto any type of telecommunications or data network including, withoutlimitation, hybrid fiber coax (HFC) networks, satellite networks, telconetworks, and data networks (including MANs, WANs, LANs, WLANs,internets, and intranets). Such networks or portions thereof may utilizeany one or more different topologies (e.g., ring, bus, star, loop,etc.), transmission media (e.g., wired/RF cable, RF wireless, millimeterwave, optical, etc.) and/or communications or networking protocols(e.g., SONET, DOCSIS, IEEE Std. 802.3, ATM, X.25, Frame Relay, 3GPP,3GPP2, WAP, SIP, UDP, FTP, RTP/RTCP, H.323, etc.).

As used herein, the term “network interface” refers to any signal ordata interface with a component or network including, withoutlimitation, those of the FireWire (e.g., FW400, FW800, etc.), USB (e.g.,USB 2.0, 3.0. OTG), Ethernet (e.g., 10/100, 10/100/1000 (GigabitEthernet), 10-Gig-E, etc.), MoCA, Coaxsys (e.g., TVnet™), radiofrequency tuner (e.g., in-band or OOB, cable modem, etc.), LTE/LTE-A,Wi-Fi (802.11), WiMAX (802.16), Z-wave, PAN (e.g., 802.15), or powerline carrier (PLC) families.

As used herein, the term “QAM” refers to modulation schemes used forsending signals over e.g., cable or other networks. Such modulationscheme might use any constellation level (e.g. QPSK, 16-QAM, 64-QAM,256-QAM, etc.) depending on details of a network. A QAM may also referto a physical channel modulated according to the schemes.

As used herein, the term “server” refers to any computerized component,system or entity regardless of form which is adapted to provide data,files, applications, content, or other services to one or more otherdevices or entities on a computer network.

As used herein, the term “storage” refers to without limitation computerhard drives, DVR device, memory, RAID devices or arrays, optical media(e.g., CD-ROMs, Laserdiscs, Blu-Ray, etc.), or any other devices ormedia capable of storing content or other information.

As used herein, the term “Wi-Fi” refers to, without limitation and asapplicable, any of the variants of IEEE Std. 802.11 or related standardsincluding 802.11 a/b/g/n/s/v/ac or 802.11-2012/2013, as well as Wi-FiDirect (including inter alia, the “Wi-Fi Peer-to-Peer (P2P)Specification”, incorporated herein by reference in its entirety).

As used herein, the term “wireless” means any wireless signal, data,communication, or other interface including without limitation Wi-Fi,Bluetooth, 3G (3GPP/3GPP2), HSDPA/HSUPA, TDMA, CDMA (e.g., IS-95A,WCDMA, etc.), FHSS, DSSS, GSM, PAN/802.15, WiMAX (802.16), 802.20,Zigbee®, Z-wave, narrowband/FDMA, OFDM, PCS/DCS,LTE/LTE-A/LTE-U/LTE-LAA, analog cellular, CDPD, satellite systems,millimeter wave or microwave systems, acoustic, and infrared (i.e.,IrDA).

OVERVIEW

A connection management mechanism for a network access technology may beinadequate in the presence of another competing network accesstechnology that employs a more aggressive connection mechanism,especially within the context of a public venue or consumer premisesenvironment. The present disclosure provides, inter alia, an“intelligent” network controller and associated architecture thatenables connectivity to a given network while coexisting with anothercompeting or even interfering network access technology.

In one exemplary embodiment of the present disclosure, a wireless localarea network (WLAN) associated with a managed content delivery networkis configured to provide an “aggressive” or preferential networkconnectivity (e.g., to the Internet or intranets) to client devices(e.g., smartphones, laptops, tablets, or smartwatches) via one or morewireless access points. The wireless access points may include forinstance Wi-Fi access points (APs) within a given venue or premises, theWi-Fi APs being configured to provide enhanced Wi-Fi connectivity toclient devices within range of the APs, while coexisting with anothernetwork access technology such as LTE-U or LTE-LAA (the latter providingservice via cellular towers, small cells, etc.) nearby or within thesame venue.

Wi-Fi protocols typically do not allow an AP or other device to encroachon a channel when there may be another network attempting to use thechannel. The present disclosure describes methods, apparatus and systemsfor prioritizing accesses between networks via a change in connectionmechanisms of one of the networks. In one implementation, operation ofWLAN access points and/or client devices are modified in order toprovide a desired connection “profile” and procedure for one of thenetwork access technologies (e.g., the Wi-Fi WLAN) so as to achieve adesired result, the latter which may be e.g., a more aggressive WLANconnection protocol in certain prescribed circumstances.

In one exemplary configuration, a dedicated background scanner devicelocated in the venue continually scans for signals from multiple radioaccess technologies (RATs), such as Wi-Fi, LTE-U and LTE-LAA occupyingthe same frequency band and/or channel(s). The background scanner sendsreports to a backend controller (e.g., a Coexistence Controller (CC))that manages the Wi-Fi APs. The controller is in data communication witha backend connection manager (CM) provisioning server, as well as adatabase that stores configuration files associated with known APs. TheCM server sends (e.g., “pushes”) to the controller, or the controllermay retrieve or pull from the CM server or database(s), configurationdata associated with a WLAN AP that is serving client devices and thatmay be excluded from providing such service by virtue of a moreaggressive connection mechanism by another RAT, e.g., LTE-U or LTE-LAA.

In one implementation, the CC modifies one or more connectivityparameters or characteristics for the AP of the affected RAT (e.g.,Wi-Fi), such as transmit power (e.g., increase signal strength), energydetection (ED) threshold (e.g., decrease to −80 dBm), frequency orchannel used (e.g., switch from 5 GHz to another frequency), beamformsettings, physical configuration of antennas, modulation scheme,handover criteria, etc. The CC then sends the modified transmitparameters (contained in a data structure such as a configuration file)to the AP, thereby causing the modified parameters to be implemented atthe AP and/or client devices. Modified parameters may later be disabledor overridden with original or yet other configurations.

The solutions provided by the exemplary embodiments advantageouslyselectively sidestep the typical back-off mechanism for cautiousprotocols (e.g., those of Wi-Fi), and allow service providers (such asMSO networks) and their users or subscribers in the venue to, interalia, utilize the services with sufficient availability and bandwidth,obtain convenient access to subscribed media content, and save batterypower (e.g., by obviating the need to constantly seek connections orswitching networks).

A service provider may also capture new ad hoc users by offering a morelevel or accessible opportunity to utilize its services among competingRATs.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Exemplary embodiments of the apparatus and methods of the presentdisclosure are now described in detail. While these exemplaryembodiments are described in the context of the previously mentionedWLANs associated with a managed network (e.g., hybrid fiber coax (HFC)cable architecture having a multiple systems operator (MSO), digitalnetworking capability, IP delivery capability, and a plurality of clientdevices), the general principles and advantages of the disclosure may beextended to other types of radio access technologies (“RATs”), networksand architectures that are configured to deliver digital data (e.g.,text, images, games, software applications, video and/or audio). Suchother networks or architectures may be broadband, narrowband, orotherwise, the following therefore being merely exemplary in nature.

It will also be appreciated that while described generally in thecontext of a network providing service to a customer or consumer or enduser (i.e., within a prescribed venue, or other type of premises), thepresent disclosure may be readily adapted to other types of environmentsincluding, e.g., outdoors, commercial/retail, or enterprise domain(e.g., businesses), and government/military applications. Myriad otherapplications are possible.

Also, while certain aspects are described primarily in the context ofthe well-known Internet Protocol (described in, inter alia, InternetProtocol DARPA Internet Program Protocol Specification, IETF RCF 791(September 1981) and Deering et al., Internet Protocol, Version 6 (IPv6)Specification, IETF RFC 2460 (December 1998), each of which isincorporated herein by reference in its entirety), it will beappreciated that the present disclosure may utilize other types ofprotocols (and in fact bearer networks to include other internets andintranets) to implement the described functionality.

Other features and advantages of the present disclosure will immediatelybe recognized by persons of ordinary skill in the art with reference tothe attached drawings and detailed description of exemplary embodimentsas given below.

Service Provider Network—

FIG. 1 illustrates a typical service provider network configurationuseful with the features of the Wi-Fi-based wireless network(s)described herein. This service provider network 100 is used in oneembodiment of the disclosure to provide backbone and Internet accessfrom the service provider's wireless access points (e.g., Wi-Fi APs orbase stations operated or maintained by the service provider or itscustomers/subscribers), one or more cable modems (CMs) in datacommunication therewith, or even third party access points accessible tothe service provider via, e.g., an interposed network such as theInternet (e.g., with appropriate permissions from the access pointowner/operator/user).

As opposed to an unmanaged network, the managed service-provider networkof FIG. 1 advantageously allows, inter alia, control and management of agiven user's access (such user which may be a network subscriber, ormerely an incidental/opportunistic user of the service) via the wirelessaccess point(s), including imposition and/or reconfiguration of variousaccess “rules” or other configurations applied to the wireless accesspoints. For example, the service provider network 100 allows componentsat the venue of interest (e.g., Wi-Fi APs and any supportinginfrastructure such as routers, switches, etc.) to be remotelyreconfigured by the network MSO, based on e.g., prevailing operationalconditions in the network, changes in user population and/or makeup ofusers at the venue, business models (e.g., to maximize profitability orprovide other benefits such as enhanced user experience, as describedinfra), etc.

In certain embodiments, the service provider network also advantageouslypermits the aggregation and/or analysis of subscriber- oraccount-specific data (including inter alia, particular mobile devicesassociated with such subscriber or accounts) as part of the provision ofservices to users under the exemplary delivery models described herein.As but one example, device specific IDs (e.g., MAC address or the like)can be cross-correlated to MSO subscriber data maintained at e.g., thenetwork headend(s) so as to permit or at least facilitate, among otherthings, (i) user authentication; (ii) correlation of aspects of theevent or venue to particular subscriber demographics, such as fordelivery of targeted advertising; and (iii) determination ofsubscription level, and hence subscriber privileges and access tocontent/features. Moreover, device profiles for particular user devicescan be maintained by the MSO, such that the MSO (or its automated proxyprocesses) can model the user device for wireless capabilities.

The wireless access points (see discussion of FIG. 1a infra) disposed atthe service location(s) (e.g., venue(s) of interest) can be coupled tothe bearer managed network (FIG. 1) via, e.g., a cable modem terminationsystem (CMTS) and associated local DOCSIS cable modem (CM), a wirelessbearer medium (e.g., an 802.16 WiMAX system), a fiber-based system suchas FiOS or similar, a third-party medium which the managed networkoperator has access to (which may include any of the foregoing), or yetother means.

Advantageously, the service provider network 100 also allows componentsat the service location (e.g., Wi-Fi APs and any supportinginfrastructure such as routers, switches, etc.) to be remotelyreconfigured by the network MSO, based on, e.g., prevailing operationalconditions in the network, changes in user population and/or makeup ofusers at the service location, business models (e.g., to maximizeprofitability), etc. In certain embodiments, the service providernetwork also advantageously permits the aggregation and/or analysis ofsubscriber- or account-specific data (including inter alia, particularmobile devices associated with such subscriber or accounts) as part ofthe provision of services to users under the exemplary delivery modelsdescribed herein.

The various components of the exemplary embodiment of the network 100include (i) one or more data and application origination sources 102;(ii) one or more content sources 103, (iii) one or more applicationdistribution servers 104; (iv) one or more video-on-demand (VOD) servers105, (v) client devices 106, (vi) one or more routers 108, (vii) one ormore wireless access point controllers 110 (may be placed more locallyas shown or in the headend or “core” portion of network), (viii) one ormore cable modems 112, and/or (ix) one or more access points 114 (whichmay or may not include embedded cable modems 113 as shown). Theapplication server(s) 104, VOD servers 105 and client device(s) 106 areconnected via a bearer (e.g., HFC) network 101. A simple architecturecomprising one of each of certain components 102, 103, 104, 105, 108,110 is shown in FIG. 1 for simplicity, although it will be recognizedthat comparable architectures with multiple origination sources,distribution servers, VOD servers, controllers, and/or client devices(as well as different network topologies) may be utilized consistentwith the present disclosure. For example, the headend architecture ofFIG. 1a (described in greater detail below), or others, may be used.

It is also noted that cable network architecture is typically a“tree-and-branch” structure, and hence multiple tiered APs may be linkedto each other or cascaded via such structure.

FIG. 1a shows one exemplary embodiment of a headend architecture. Asshown in FIG. 1a , the headend architecture 150 comprises typicalheadend components and services including billing module 152, subscribermanagement system (SMS) and client configuration management module 154,cable modem termination system (CMTS) and OOB system 156, as well asLAN(s) 158, 160 placing the various components in data communicationwith one another. It will be appreciated that while a bar or bus LANtopology is illustrated, any number of other arrangements as previouslyreferenced (e.g., ring, star, etc.) may be used consistent with thedisclosure. It will also be appreciated that the headend configurationdepicted in FIG. 1a is high-level, conceptual architecture, and thateach MSO may have multiple headends deployed using custom architectures.

The exemplary architecture 150 of FIG. 1a further includes a conditionalaccess system (CAS) 157 and a multiplexer-encrypter-modulator (MEM) 162coupled to the HFC network 101 adapted to process or condition contentfor transmission over the network. The distribution servers 164 arecoupled to the LAN 160, which provides access to the MEM 162 and network101 via one or more file servers 170. The VOD servers 105 are coupled tothe LAN 160 as well, although other architectures may be employed (suchas for example where the VOD servers are associated with a coreswitching device such as an 802.3z Gigabit Ethernet device). Aspreviously described, information is carried across multiple channels.Thus, the headend must be adapted to acquire the information for thecarried channels from various sources. Typically, the channels beingdelivered from the headend 150 to the client devices 106 (“downstream”)are multiplexed together in the headend, as previously described andsent to neighborhood hubs (as shown in the exemplary scheme of FIG. 1b )via a variety of interposed network components. As shown in FIG. 1b ,the network 101 of FIGS. 1 and 1 a comprises a fiber/coax arrangementwherein the output of the MEM 162 of FIG. 1a is transferred to theoptical domain (such as via an optical transceiver 177 at the headend orfurther downstream). The optical domain signals are then distributed toa fiber node 178, which further distributes the signals over adistribution network 180 to a plurality of local servicing nodes 182.This provides an effective 1:N expansion of the network at the localservice end. It will be appreciated that the CPE 106 shown in FIG. 1bmay in fact comprise CMTS or other devices such as the embedded cablemodem AP 206, or wireless APs 202, 204, 206, 208 disposed within one ormore venues, as described subsequently herein with respect to FIGS. 2-2a.

FIG. 1c illustrates an exemplary “switched” network architecture.Specifically, the headend 150 contains switched broadcast control 190and media path functions 192; these element cooperating to control andfeed, respectively, downstream or edge switching devices 194 at the hubsite which are used to selectively switch broadcast streams to variousservice groups. Broadcast switched architecture (BSA) media path 192 mayinclude a staging processor 195, source programs, and bulk encryption incommunication with a switch 275. A BSA server 196 is also disposed atthe hub site, and implements functions related to switching andbandwidth conservation (in conjunction with a management entity 198disposed at the headend). An optical transport ring 197 is utilized todistribute the dense wave-division multiplexed (DWDM) optical signals toeach hub in an efficient fashion.

In addition to “broadcast” content (e.g., video programming), thesystems of FIGS. 1a and 1c (and 1 d discussed below) also deliverInternet data services using Internet Protocol (IP), although otherprotocols and transport mechanisms of the type well known in the digitalcommunication art may be substituted. One exemplary delivery paradigmcomprises delivering MPEG-based video content, with the videotransported to user client devices (including IP-based STBs orIP-enabled consumer devices) over the aforementioned DOCSIS channelscomprising MPEG (or other video codec such as H.264 or AVC) over IP overMPEG. That is, the higher layer MPEG- or other encoded content isencapsulated using an IP protocol, which then utilizes an MPEGpacketization of the type well known in the art for delivery over the RFchannels. In this fashion, a parallel delivery mode to the normalbroadcast delivery exists, i.e., delivery of video content both overtraditional downstream QAMs to the tuner of the user's STB or otherreceiver device for viewing on the television, and also as packetized IPdata over the DOCSIS QAMs to the user's client device or otherIP-enabled device via the user's cable modem. Delivery in suchpacketized modes may be unicast, multicast, or broadcast.

Referring again to FIG. 1c , the IP packets associated with Internetservices are received by the edge switch 194, and in one embodimentforwarded to the cable modem termination system (CMTS) 199. The CMTSexamines the packets, and forwards packets intended for the localnetwork to the edge switch 194. Other packets are discarded or routed toanother component. As an aside, a cable modem is used to interface witha network counterpart (e.g., CMTS) so as to permit two-way broadbanddata service between the network and users within a given service group,such service which may be symmetric or asymmetric as desired (e.g.,downstream bandwidth/capabilities/configurations may or may not bedifferent than those of the upstream).

The edge switch 194 forwards the packets received from the CMTS 199 tothe QAM modulator, which transmits the packets on one or more physical(QAM-modulated RF) channels to the client devices. The IP packets aretypically transmitted on RF channels (e.g., DOCSIS QAMs) that aredifferent that the RF channels used for the broadcast video and audioprogramming, although this is not a requirement. The client devices 106are each configured to monitor the particular assigned RF channel (suchas via a port or socket ID/address, or other such mechanism) for IPpackets intended for the subscriber premises/address that they serve.For example, in one embodiment, a business customer premises obtains itsInternet access (such as for a connected Wi-Fi AP) via a DOCSIS cablemodem or other device capable of utilizing the cable “drop” to thepremises (e.g., a premises gateway, etc.).

While the foregoing network architectures described herein can (and infact do) carry packetized content (e.g., IP over MPEG for high-speeddata or Internet TV, MPEG2 packet content over QAM for MPTS, etc.), theyare often not optimized for such delivery. Hence, in accordance withanother embodiment of the disclosure, a “packet optimized” deliverynetwork is used for carriage of the packet content (e.g., Internet data,IPTV content, etc.). FIG. 1d illustrates one exemplary implementation ofsuch a network, in the context of a 3GPP IMS (IP Multimedia Subsystem)network with common control plane and service delivery platform (SDP),as described in co-owned and co-pending U.S. patent application Ser. No.12/764,746 filed Apr. 21, 2010 and entitled “METHODS AND APPARATUS FORPACKETIZED CONTENT DELIVERY OVER A CONTENT DELIVERY NETWORK”, which isnow published as U.S. Patent Application Publication No. 2011/0103374 ofthe same title, incorporated herein by reference in its entirety. Such anetwork provides, inter alia, significant enhancements in terms ofcommon control of different services, implementation and management ofcontent delivery sessions according to unicast or multicast models,etc.; however, it is appreciated that the various features of thepresent disclosure are in no way limited to this or any of the otherforegoing architectures.

It will be appreciated that the foregoing MSO or managed network canadvantageously be leveraged for easy installation of the various APs(and/or any lower-level “children APs” as described in co-owned U.S.patent application Ser. No. 15/002,232 entitled “APPARATUS AND METHODFOR WIRELESS SERVICES IN MOVING VEHICLES” filed Jan. 20, 2016, andissued as U.S. Pat. No. 9,918,345 on Mar. 13, 2018, incorporated supra)within a geographic region. Consider, for example, a MSO network that isalready pervasive throughout a given area (i.e., the MSO has numerouscustomers, both business and residential and otherwise); in suchnetworks, the MSO already has significant infrastructure deployed, at avery high level of granularity. Hence, if an AP needs to be placed at agiven location in order to effect the coverage/operation for the Wi-Finetwork described herein (e.g., for an impromptu concert or event heldat a location not associated with any particular venue structure), theMSO can easily “tap off′ the existing infrastructure in that area toenable the ad hoc AP placement. This may take the form of e.g.,placement of an AP coincident with a given customer's extant equipment,and/or placement of new equipment that taps off a local service node.

It is also contemplated that the service provider may utilize or“piggyback” off the existing infrastructure or infrastructure of otherservice providers, utilities, etc. For instance, a third party serviceprovider may have a high-bandwidth backhaul “drop” near a location orvenue desired by the MSO; the MSO can then lease, pay, rent, etc. thatthird party for temporary use of the drop (e.g., for the duration of theevent). Similarly, traffic signal poles, lighting, bridges, tunnels,etc. all contain a wide variety of cabling, conduits, and otherinfrastructure which the (host) MSO could make use of so as to obviatehaving to perform a new installation (and all of the attendant costs anddelays thereof).

Network addressing in such “composite” or “parent/child” scenarios mayassign each node of a network with an address that is unique to thatnetwork; the address can be used to communicate (directly viapeer-to-peer communications, or indirectly via a series of “hops”) withthe corresponding device. In more complex networks, multiple layers ofindirection may be used to assist in address exhaustion (e.g., oneaddress is logically divided into another range of network addresses).Common examples of network routing protocols include: Internet Protocol(IP), Internetwork Packet Exchange (IPX), and OSI-based networktechnologies (e.g., Asynchronous Transfer Mode (ATM), SynchronousOptical Networking (SONET), Synchronous Digital Hierarchy (SDH), andFrame Relay.

As is described in further detail infra, a dedicated AP may beconfigured to, e.g., scan for and detect background signals associatedwith one or more RATs (Wi-Fi, LTE-U, LTE-LAA, etc.) and reportinformation and statistics to the backend, but not necessarily transmitdata to client devices. Such a dedicated AP may be newly installed ordeployed in the field, a replacement of extant equipment at a convenientnode, and/or repurposed from extant equipment, so as to enable the MSOto piggyback off existing infrastructure as described above.

Even with the myriad equipment implementations allowing an end user toaccess WLAN services (e.g., via APs, modems, intermediate entities,towers), some telecommunications providers have set up LTE services thatare broadly available, including significant coverage in most areas ofthe developed world. In certain cases, this setup, in combination withLTE's comparatively aggressive connection mechanism that is dependent ona relatively lower signal detection threshold, causes client devices totransmit data over LTE rather than Wi-Fi in the same frequency band(e.g., 5 GHz), particularly in public venues without a trusted AP (e.g.,a known home or office modem).

This results in the aforementioned problems with respect to LTEprioritization; i.e., even when WLAN services are available and moredesirable for a particular use case, the user equipment is “forced” intousing LTE data, thereby potentially invoking additional costs, batteryconsumption, and other undesired effects.

Hence, given the desire for constant access to the Internet byconsumers, current mechanisms for arbitrating between RATs (e.g., Wi-Fiand LTE-U/LTE-LAA) present challenges to the MSO (or dedicated portionsthereof, such as AP controller, CMTS, etc.) to optimize its services toclient devices. The present disclosure addresses these challenges byselectively controlling access to those RATs based at least in part onfunctionality obtained from a backend entity (e.g., a controllerapparatus), as described in greater detail below.

Wireless Services Architecture—

FIG. 2 illustrates an exemplary embodiment of a network architecture 200useful in implementing the wireless RAT co-existence methods of thepresent disclosure. As used in the present context, the term “users” mayinclude without limitation end users (e.g., individuals, whethersubscribers of the MSO network or not), venue operators, third partyservice providers, or even entities within the MSO itself (e.g., aparticular department, system or processing entity).

As shown, the architecture generally includes a networked (i.e., “cloud”based) provisioning server 201 (locally resident with a co-existencecontroller 210, or remotely at the backend or headend of the system),one or more access points 202, 204, 206, 208 in data communication withthe coexistence controller (CC) 210 (e.g., via existing networkarchitectures including any wired or wireless connection), as well asany number of client devices 212 (smartphones, laptops, tablets,watches, vehicles, etc.) which may or may not be within range of an APthat is served by the coexistence controller 210. The client devices mayalso have different capabilities (e.g., as “nodes” of the networkthemselves, as described in greater detail infra).

A client device database 203 is also provided, wherein the clientmanagement provisioning server 201 can access and store data relatingto, inter alia: (i) individual client devices, such as MAC address orother specific identifying information, (ii) any associated subscriberaccounts or records, (iii) the WLAN configuration of the client, (e.g.,supported Wi-Fi variants, MCS, MIMO capability, etc.), and (iv) themulti-RAT provisioning status of the particular client (e.g., whetherthe client has had the CM 221 installed, status of “pushed”configuration data to the installed CM, etc.).

Also included are one or more RF scanner devices 214, 216, 218 which, asdescribed in greater detail elsewhere herein, help the coexistencecontroller (CC) 210 characterize the radio frequency spectrum andenvironment in which the APs operate, so as to enable selective client(and/or AP) configuration changes to enhance WLAN prioritization overcompeting RATs.

An AP environment profile database 205 is also included in thearchitecture of FIG. 2, and is in communication with the CC 210 viae.g., a wired or wireless data interface. The AP DB 205 in theillustrated embodiment retains data relating to, among other things: (i)AP identification (e.g., MAC), (ii) AP location, (iii) association withparent or child nodes or networks (if any), (iv) association of an APand one or more scanners, and (v) AP WLAN configuration and capabilitiesdata.

In certain embodiments, each AP 202, 204, 206, 208 is located withinand/or services one or more areas within one or more venues (e.g., abuilding, room, or plaza for commercial, corporate, academic purposes,and/or any other space suitable for Wi-Fi access). Each AP is configuredto provide wireless network coverage within its coverage or connectivityrange 220, 222, 224. For example, a venue may have a wireless modeminstalled within the entrance thereof for prospective customers toconnect to, including those in the parking lot via inter alia, theirWi-Fi enabled vehicles or personal devices of operators thereof.

In one implementation, the system and methods of the present disclosureinclude determining a desired or optimal installation configuration forone or more wireless interface devices (e.g., APs) within a premises orvenue, such as for example using the methods and apparatus described inco-owned and co-pending U.S. patent application Ser. No. 14/534,067filed Nov. 5, 2014 and entitled “METHODS AND APPARATUS FOR DETERMININGAN OPTIMIZED WIRELESS INTERFACE INSTALLATION CONFIGURATION”. Asdisclosed therein, a network entity collects information relating to thetype of services required, and generates a customer profile. Thecustomer profile is then used to determine a number and type of wirelessinterface devices required. In one variant, a device chart is generated,which lists a plurality of combinations of categories of service and arespective plurality of device combinations needed to provide optimal(or at least to the desired level of) service thereto. The device chartis consulted to arrive at an appropriate installation work order, whichis submitted for premises installation.

As discussed elsewhere herein, client devices may or may not be withinthe range serviced by AP(s). Additionally, some client devices may bewithin the range, and thus serviced by, only one AP (e.g., a clientdevice 213 located is within the range 224 of only access point 208),whereas some other client devices may be within range of two or more APswithin a designated area (e.g., client device 212 in may be serviced byone or both of two AP's 206, 208 as the APs' respective ranges 222, 224overlap). In one variant, APs 202, 204 may be in communication (e.g.,via direct connection by way of e.g., Gigabit Ethernet or other wiredconnection, or even over Wi-Fi (e.g., Wi-Fi Direct), as indicated byoverlapping connectivity ranges and connection 226). In one suchimplementation, a sub-network is created by utilizing the techniques toextend and enhance existing networks described in co-owned U.S. patentapplication Ser. No. 14/959,948 entitled “APPARATUS AND METHOD FORWIRELESS NETWORK EXTENSIBILITY AND ENHANCEMENT” filed Dec. 4, 2015, andissued as U.S. Pat. No. 10,327,187 on Jun. 18, 2019, incorporated byreference in its entirety. The client device 211 may be serviced by AP204, and thereby receive information stored at either or both APs 202,204 even if AP 204 is out of range. The client device 211 may also beserviced in a peer-to-peer sub-network, such as by receiving beaconsand/or connecting (e.g., tethering or acting as a relay) with anotherclient device (not shown) serviced by AP 204.

In the exemplary embodiment, one or more APs 202, 204 are indirectlycontrolled by the controller 210 (i.e., via infrastructure of the MSOnetwork), while one or more APs 206, 208 are connected to (andcontrolled at least in part by) the AP co-existence controller 210directly. Various combinations of the foregoing direct and indirectcontrol may be implemented within the architecture 200 of FIG. 2 asdesired.

In some embodiments, APs of different types, such as directly controlledAPs 206, 208 (i.e., children APs) and non-directly controlled APs 202,204 may transmit data (e.g., notifications derived from the coexistencecontroller 210) to/from a client device 211, 212, 213 within theirconnectivity range as is described in e.g., co-pending and co-owned U.S.patent application Ser. No. 15/002,232, and that described in U.S.patent application Ser. No. 14/959,948, incorporated supra. The clientdevices 211, 212, 213 can be in range of an non-local or parent AP 204,202 as well as a local or child AP 206, 208.

In an exemplary implementation, the client devices 211, 212, 213 eachinclude a connection manager (CM) application computer program 221operative to run on the client and, inter alia, enable the host clientdevice to alter its WLAN configuration in order to enable more“competitive” or selective WLAN services in a multi-RAT environment, asdescribed in greater detail below.

In one or more embodiments, the APs may also provide various informationvia an open-access network such as a wireless local area network (WLAN),such as that described in co-owned U.S. patent application Ser. No.15/063,314 filed Mar. 7, 2016 entitled “APPARATUS AND METHODS FORDYNAMIC OPEN-ACCESS NETWORKS”, and issued as U.S. Pat. No. 10,492,034 onNov. 26, 2019, incorporated by reference in its entirety. In oneembodiment, the information provided is contextually relevant tolocations of respective users or devices receiving the information. Asbut one example, the information provided may relate to the availabilityof WLAN performance enhancement via use of an API; i.e., advertising tothe client (via its indigenous protocol stack or communicationscapabilities), the ability to obtain better WLAN performance withininter alia, the venue or service area by accessing the designated API bywhich the provisioning server can authenticate the client device andinstall the CM application or module 221).

In one implementation, the information is provisioned by a networkentity (for example, from a service provider network operator) andprovided to one or more access points (APs) of the service providernetwork. The information is bit-stuffed into Wi-Fi beacon frames orother data structures that are broadcast by the APs to nearby clientdevices. A receiving client device extracts the information using aprotocol embodied in the OS or extant software of the client, and mayalso initiate a dedicated wireless connection with the AP for e.g.,transmission of the CM 221 as a download, or a URL or other networkaddress where the client can obtain the CM 221 from the provisioningserver 201.

Alternatively, if the CM 221 has already been installed on the givenclient device, the installed CM 221 can be used to extract data from the“stuffed” beacons relating to other functions of interest to the user.

Turning now to the coexistence controller 210, in one or moreembodiments, controller 210 is configured to dynamically monitor RFconditions and performance information in the hosting environment viause of the APs 202, 204, 206, 208 and/or the scanner(s) 214, 216, 218.

FIG. 2a illustrates an exemplary cable network architecture forproviding WLAN services within, e.g., a venue or other premises, whichextends from user client devices within the venue to, inter alia, datacenters. In the exemplary embodiment, the architecture 230 is dividedinto four main logical groups: an access network 232, a regional datacenter 234, a national data center 236, and a service platform 238. Theaccess network 232 includes one or more APs (e.g., wireless APs 204,206, 208) disposed within the venue, and end users 211 connected theretovia client devices. The regional data center 234 assists in providingservices to the end users 241 by receiving, transmitting, and processingdata between the access network 232 and the backbone 242 of the cablenetwork. In one embodiment, the regional data center 234 is a localinfrastructure that includes controllers (e.g., AP controllers),switches, policy servers and network address translators (NATs) incommunication with the backbone 242. The regional data center 234 maybe, for example, an intermediate data center on premises disposed awayfrom the local APs and user premises (venue), and disposed within alarger infrastructure.

In the exemplary embodiment, the backbone 242 of the network enablesdata communication and services between the regional data center 234 andthe national data center 236 via backhaul, and/or connection to the(public) Internet 111. In one implementation, the national data center236 provides further top-level provisioning services to the regionaldata center 234 (e.g., load balancing, support of Trivial File TransferProtocols (TFTP), Lightweight Directory Access Protocols (LDAP), andDynamic Host Configuration Protocols (DHCP)), as well as providing thesame to other data centers and/or access networks which may be part ofthe network operator's (e.g., MSO's) national-level architecture. Thenational data center 236 also houses in one embodiment more advancedbackend apparatus (e.g., CMTS 199, AP controllers, Layer 3 switches, andservers for the provisioning services). In one embodiment, a separateservice platform 238 may provide auxiliary services to the end userswithin the venue and subscribed to the MSO network provider, includingaccess to mail exchange servers, remote storage, etc. Thus, it can beappreciated that myriad network nodes and entities, as well asconnections there between, enable client devices (and ultimately endusers 211) to maintain end-to-end connectivity across the network.

Extant WLAN and Multi-RAT Implementation Scenarios—

FIG. 3 illustrates a Wi-Fi back-off mechanism for collision avoidance asis typically implemented in prior art WLAN (e.g., Wi-Fi) technologyapplications. More directly, a Wi-Fi carrier-sense multiple access withcollision avoidance (“CSMA/CA”) network access mechanism is shown. Inparticular, when a first network node or station receives a packet to besent to another node or station, Wi-Fi (according to, e.g., theprevailing 802.11 standard under which the system operates) initiatesphysical carrier sensing and virtual carrier sensing mechanisms todetermine whether the medium (e.g., a channel and/or frequency used bythe Wi-Fi transceiver) is busy or occupied by other transmissions.Hence, two (2) mechanisms are specified to determine if the Wi-Fichannel is busy; physical and virtual carrier sensing.

Physical carrier sensing may be performed for instance by a physicallayer (PHY) that includes a clear channel assessment (CCA) function. CCAmay include carrier sense (CS) and energy detection (ED) functions. CSallows the first node (intending to send the packet) to determine aperiod of time during which the medium will be busy. ED may detectwireless signals other than those originated or relating to Wi-Ficompliant devices based on a detection threshold above that of Wi-Fi.Using one or more of these functions, the CCA may assess whether themedium is idle; if not, the physical layer logical process waits untilthe medium is clear.

Virtual carrier sensing may involve setting a network allocation vector(NAV), whose functions include a counter. The counter may indicate howlong the node is to consider the medium busy. In other words, the nodemay make a “best guess” as to how long the medium will be busy before itmay transmit the packet. When the NAV is zero, the medium is assumed tobe idle, i.e., there are no other nodes attempting to transmit a packet.When NAV is not zero, it indicates that the medium is busy, e.g., thenode is transmitting a packet. In some cases, virtual carrier sensingmay limit the need for physical carrier sensing, such as to save power.For instance, the node station may go to sleep until NAV reaches zero,after which it wakes up to check whether the medium is busy or idle.

In addition to the conditions set by physical carrier sensing andvirtual carrier sensing, the Wi-Fi CSMA/CA may impose further checks bya node to ensure that the channel on which the packet is to be sent isclear. That is, an “extra polite” wait duration is imposed to determinewhether the medium is idle. If the channel is not clear, andtransmission attempted, there is a “collision” with the signal ofanother node, and the first node waits a certain period of time (i.e., aback-off value or back-off factor) before re-attempting access of themedium. The period of time may be chosen to be e.g., a random timeperiod, or a progressively increasing backoff period based on subsequentcollisions. After the conditions for retry are met (e.g., NAV is zero),the node checks to see if the medium is idle at the time of the check.If not, another back-off value is set. In different implementations,this value may be set to be a smaller value, a larger value, the samevalue, another random value, or according to yet another scheme. FIG. 3illustrates an exemplary decreasing back-off value scheme.

The foregoing process repeats until the channel is clear and the “extrapolite” back-off conditions have been met, at which point the packet isready for transmission. The packet is sent to the other receiving node,and a timer may be set for an ACK signal. If the ACK is received beforethe time expires, the transmission of the packet was successful. If not,transmission failed.

In contrast, LTE-U collision avoidance mechanisms are less cautious, andmay dominate access to a channel in a situation where LTE-U coexistswith Wi-Fi wireless access points (APs) (and/or other LTE-U nodes),e.g., via cell towers, small cells, femto cells, base stations, eNBs(evolved NodeBs). In theory, the LTE-U node should attempt to choose afree or idle channel (i.e., not in use) in which no other LTE-U node orWi-Fi AP is operating; if a free channel is not found, the LTE-U nodeshould apply duty cycle procedures that allow the node to share achannel with Wi-Fi and other LTE-U signals. In some circumstances, dutycycling parameters may be adapted to usage of other signals, e.g., inresponse to Wi-Fi usage.

However, in practice, a potential issue with such a coexistence schemeis that equipment vendors may not follow the “friendly” mechanisms asoutlined above, causing LTE-U to benefit more; e.g., create moreconnections that are stronger and more persistent (and which favormacro-network operators) compared to Wi-Fi. For instance, LTE-Uequipment may allow a non-standard duty cycle that favors LTE-U overneighboring wireless technologies such as Wi-Fi (which uses theaforementioned “extra polite” back-off mechanism as described supra).This may result in degraded performance and user experience withwireless services provided by Wi-Fi APs in the same venue or area,including low data throughput (rate) and high latency, as well asfrequent “dropping” of Wi-Fi connections between the client and the AP.

Similarly, LTE-LAA in theory should follow a standard listen-before-talk(LBT) procedure that is similar to Wi-Fi's conservative design (i.e.,one in which an access point is to hold off transmissions until themedium is clear and/or signal strength falls below a threshold, inaddition to an extra back-off time period). However, in practice,LTE-LAA equipment vendors may also deviate from LBT algorithms, and useback-off windows that deviate from more cautious settings. In oneexample, LTE-LAA equipment (e.g., a small cell) may perform a non-zeroback-off period. As such, if a Wi-Fi access point coexists (i.e., isdeployed in the same general venue) with such a “modified” LTE-LAA smallcell, a wireless device is more likely to obtain better access viaLTE-LAA rather than Wi-Fi on the same frequency (e.g., 5 GHz), becausetransmission will occur immediately on LTE-LAA.

Other ways that LTE-U or LTE-LAA may dominate a shared channel on anunlicensed frequency spectrum include following an exponentiallydecreasing back-off (or a fixed back-off time window) that provides anadvantage over a random back-off period employed by Wi-Fi's LBTprocedure.

Hence, it can be readily seen that the “extra polite”collision-avoidance mechanism for Wi-Fi provides ample opportunity forother RATs using the same frequency spectrum (such as LTE-U and LTE-LAA)to occupy one or more channels that could have been used to transmitdata via a Wi-Fi connection. Moreover, as previously mentioned, thesignal detection threshold for Wi-Fi may be higher than that of otherRATs, leading to a scenario in which the other RATs may more easilyoccupy the channels. See, for example, FIG. 3b as discussed infra.

FIG. 3a illustrates a typical network scenario in which only Wi-Ficonnectivity is available. In this embodiment, a wireless-enabled clientdevice (e.g., a Wi-Fi-compliant smartphone) at a venue is connected to awireless access point 302 that provides wireless network service. Inthis use case, the client device is using channel 36, which is operatingin a 5 GHz frequency band with a signal strength of −80 dBm. Where onlyWi-Fi is available, the user may access the Internet and/or othernetworks as long as the client device is within the cell edge of thenetwork; i.e., within a distance from the from the nearest AP (e.g.,access point 302) at which the client device senses a minimal signalpower level, i.e., approximately −80 dBm (decibel-milliwatts) or higher.A signal strength of approximately −85 dBm may be considered the minimumsignal strength at which basic connectivity is possible. Forconsistently reliable packet delivery, however, a signal strength of −70dBm or higher is ideal, which may be achieved by, e.g., moving thewireless device closer to the AP, or increasing the transmit power ofthe AP. Hence, the client device C1 as shown in FIG. 3a has achievedbasic connectivity to the network with a minimal signal level, and maycontinue to receive Wi-Fi service unless the signal drops belowapproximately −80 dBm.

FIG. 3b illustrates a coexistence scenario in which Wi-Fi connectivityand LTE-U and/or LTE-LAA connectivity are available. In contrast to thescenario illustrated in FIG. 3a , performance of client device such asC1 may be negatively impacted due to the presence of other RATs, such asLTE-U and/or LTE-LAA deployed within range of the client device. Forexample, in the presence of a competing RAT, the connection to Wi-Fi mayfrequently disconnect, experience low data throughput rates, experiencehigh latency, or fail to connect altogether. Any established Wi-Ficonnections may see severe performance degradation and be renderedunusable for typical activities (e.g., Web browsing, voice-over-IP(VoIP) calls, video chats, file transfers, media streaming, contentconsumption). Notably, the negative impact on Wi-Fi connectivity ispossible even under relatively good signal conditions (i.e., where Wi-Fisignal strength exceeds −80 dBm) because of the “polite” Wi-Fi back-offmechanisms as described with respect to FIG. 2 supra, unfriendlyconnection mechanisms by the other RATs (e.g., aggressive energydetection (ED) levels, open-ended connection algorithms that may beexploited by individual equipment vendors looking to push the connectionto a particular RAT) and/or other contributive factors (e.g., hard-codedsoftware settings within operating systems of client devices).

To illustrate, the scenario in FIG. 3b shows a venue with two (2) RATsdeployed, specifically Wi-Fi (providing access to a network via, e.g., aWAP 302 operated by a cable network operator) as well as LTE-U and/orLTE-LAA (providing access to a network via, e.g., a cellular tower 304operated by a mobile network operator). The Wi-Fi AP 302 seeks toprovide service to wireless-enabled client device C1 via Wi-Fi. The LTEcell tower 304 seeks to provide service to another wireless-enabledclient device C2.

Although client device C1 sees a nearly minimal signal strength of −80dBm from Wi-Fi AP 302, a user of C1 may seek to connect to the networkvia Wi-Fi for various reasons, including e.g.: (i) to perform activitiesthat require consistent bandwidth usage (e.g., VoIP calls, video chats),(ii) reduce the quota or charges against LTE “data” usage, (iii) avoidany packet delays or jitters during handovers between LTE nodes (e.g.,moving between coverage areas of small cells or towers), (iv) savebattery power while at or going to a venue without ready access to apower outlet, and/or (v) gain access to services particular to a serviceprovider of which the user is a subscriber (e.g., content or mediaexclusive to the service provider, access to email services, online orremote “cloud” storage, convenient access to billing information and/orpayment options reviewable by customers, access to support andtroubleshooting help, or interface for shopping for additional hardwareor features).

Conversely, a cable network operator or other MSO may seek topreferentially provide Wi-Fi access to its customers at a venue, and/orserve secondary content (e.g., contextually appropriate banner or otheradvertisements, sponsored video content and/or other means ofmonetization). Stated simply, the MSO or its customers (e.g., thirdparties such as advertisers, content providers, etc.) may obtain abetter ROI or more “impressions” when Wi-Fi is selectively used over sayLTE-U or LTE-LAA.

Furthermore, it is noted that a low Wi-Fi signal strength does notnecessarily correlate to a low connection speed; assuming the Wi-Ficonnection between an access point and a client device is stabilized, itmay be possible to perform comparatively high-speed browsing, filetransfers, or other operations.

Hence, there are various circumstances or reasons that a client deviceor its user (and/or a service provider) might prefer use of Wi-Fi.

However, the presence of the second RAT (provided by LTE cell tower 304)may cause a signal collision on the same channel 36 on the samefrequency band (e.g., 5.0 GHz) used by the Wi-Fi AP 302. The collisionmay be due to various factors. The LTE tower 304 may be operating a moreaggressive connection mechanism. Alternatively (or in addition), the LTEtower 304 may be operating at a transmit power or threshold similar tothat typically used for Wi-Fi, or where the signal strength of LTEexceeds that of Wi-Fi, such as −73 dBm (which is higher than the typicalminimal Wi-Fi connectivity threshold). The higher transmit power may beby virtue of, inter alia, having a relatively larger geographiccoverage, and capabilities to provide connectivity to thousands of usersper tower. Thus, in a coexistence scenario such as the one describedwith respect to FIG. 3b , one or more of the aforementioned factors maycause the connection management function of the client device C1 (e.g.,an O/S based connection manager class within the Java-based Android O/Ssuch as “Context.getSystemService(Context.CONNECTIVITY SERVICE)”) totreat LTE as more “accessible” (or even as the only viable option),thereby causing the client device C1 to prioritize LTE and connect tothe LTE service.

Hence, the present disclosure sets forth various embodiments of methodsand apparatus to enable a RAT-aware networked system such as that ofFIGS. 2-2 a to, inter alia, apply a dynamic change in connectionmechanisms of access points and/or client devices, in order to provide amore selective and controlled connectivity procedure for one or morecoexisting RATs.

FIG. 4 is a high-level logical diagram illustrating operation of thenetwork architecture 200 of FIGS. 2-2 a to selectively control Wi-Ficonnection within a venue or environment deploying coexisting Wi-Fi andLTE-U or LTE-LAA services. More specifically, in illustrated example,the coexistence controller 210 communicates with: (i) the backgroundscanner 214, which monitors the local or venue service area 416(including the coverage areas of the APs 204, 206 and the coverage areaof the LTE cell station 408) to characterize the RF environment of theservice area 416; and (ii) the in-venue APs 204, 206, to apply dynamicchanges as needed to one or more of the APs, and also optionally the CMapps 221 on the clients with which the APs communicate.

As shown in FIG. 4, Wi-Fi may coexist with LTE-U or LTE-LAA serviced by,e.g., at least one LTE cell tower 408.

In the exemplary embodiment, the dedicated background scanner 214comprises an RF sensor configured in an “access point” hardwareenvironment (that is, basically an AP without the AP functionality,although as described in greater detail below, the present disclosurecontemplates both (i) co-location of the scanner 214 with an AP; and/or(ii) use of an AP as a scanner in certain operating modes). The RFsensor is configured to scan and detect signals that are propagatingwithin the venue (e.g., Wi-Fi signals, LTE signals, and/or other radiosignals in the frequency band(s) of interest) that may potentially beused by wireless client devices (e.g., smartphones, laptops, tablets,“roaming” devices, and other mobile user devices in the venue)—in effectacting as a RAT detector. The scanner 214 may comprise one or moreantennas and/or transceivers, although it may in certain embodiments beas simple as an RF receiver and single (non-MIMO) antenna. Distinct fromWi-Fi APs 204 and 206, the background scanner 214 may report networkconditions within the venue to the CC 210, but not provide connectivityto client devices in the venue. Such “dedicated” background scanner 214that does not transmit data to multiple client devices advantageouslyallows the scanner to allocate its computing and other resources todetecting and reporting relevant network characteristics to the CC 210,e.g., number and types of RATs deployed in the venue, signal levels,channel information, congestion levels, and signal noise. Whenconfigured with MIMO or MISO capability (or multiple spatially diverseantenna and receiver chains such as a phased array), the scanner 214 mayalso provide data to enable spatial resolution of the detected RFsignals; e.g., a map of RSSI or the like as a function of absolute orrelative azimuth (ϕ)—in effect an angular “heat map”. Moreover, wheretwo or more scanners 214 are utilized at different locations within thesame venue or region of interest, 2-D or even 3-D spatial resolution andmapping is possible, such as can be conducted by the CC 210 or even abackend MSO server process running a suitable algorithm to process theobtained RF data from the scanner(s) 214.

In one embodiment, the range covered by the background scanner 214 maybe based on a designated physical or virtual boundary; e.g., thebackground scanner may have a list of known access points and LTE nodeswithin the premises of a stadium, shopping mall, airport, etc. Thebackground scanner may thus be strategically positioned within the venueso as to be able to sense signals originating from various nodes, e.g.,placed in a location having relative proximity to each of the known APsand nodes, or placed away from potential signal-blocking structures suchas metallic barriers and fences.

In one implementation, the background scanner is placed near to at leastone known Wi-Fi AP and scan for all detectable signals, including thosethat might compete or interfere with the AP. For example, consider ascenario in which the background scanner 214 is placed within a servicearea 414 (FIG. 4) that is within the effective range of the Wi-Fi AP204. Such a placement allows a service provider (e.g., MSO) to detectwhether another RAT (e.g., LTE) coexists in an area where competitive“shaping” procedures should be implemented, hence giving users a greaterrange of options in terms of connectivity and activities suitable foravailable connections. In other words, the background scanner 214 issituated so as to be able to detect both Wi-Fi and LTE within range of aWi-Fi access point; a client device within the service area 414 is alsotherefore likely to see both Wi-Fi and LTE signals, and hence thescanner 214 obtains data representative of the client device experiencewithin that area 414.

In one variant, at least one background scanner 214 is placed near theedge of the venue 416, which is a location likely to experience ascenario in which a one signal (e.g., Wi-Fi) may be overwhelmed byanother (e.g., LTE) and would require control of detection thresholds,transmit power, etc. as described herein.

In another variant, at least one background scanner is located so thatit detects signals within one or more representative areas relative tothe planned users; i.e., only areas where users might actually be, or beable to utilize their client devices. For example, in one such case, anairport may have numerous areas which are not accessible to users, suchas runways, taxiways, maintenance hangers, baggage processing areas,etc. Whether users might find their WLAN competing with an LTE signal isimmaterial in these locations (and in fact, due to possible conflictwith aircraft or other facility RF systems, it may be desirable tomaintain the RF signal in certain bands as low as possible in suchareas).

In another variant, the background scanner can be configured to detectonly the type of signals which are known to be (routinely) presentwithin the venue area 416; e.g., to scan for Wi-Fi and LTE only.

As will be further described herein, in order to maintain a persistentconnection to Wi-Fi, the CC 210 may then modify transmit settingsassociated with the AP 204, 206 and/or cause one or more client devicesto adjust a detection threshold.

In some implementations, the background scanner 214 is configured toperform scanning and reporting functions via a “repurposed” wireless AP.For example, an existing AP (similar to AP 204, 206) may operate varioustypes of antennas, such as multiple-in multiple-out antennas (e.g., 2×2,3×3, 4×4, and so on), omnidirectional antennas (i.e., communication inmultiple directions, e.g., 360 degrees), patch antennas, or phasedarrays. In one variant, one or more sets of radio chains and associatedantennas within a MIMO array may be reconfigured to detect backgroundsignals, and communicate with the CC 210 via the AP backhaul. In otherwords, an AP may have one or more of multiple antennas dedicated for, oreven selectively useful for, background scanning, while other ones ofthe multiple antennas continue to provide Wi-Fi services toWi-Fi-compliant devices within range. In contrast, a “dummy” AP(scanner) that solely reports information (e.g., channel information,status report, client device information, presence of RATs) may use allof its antennas and other functionality to perform the backgroundscanning and reporting. One such “dummy” AP may comprise the exemplarydedicated background scanner 214 as shown in FIG. 4.

Nevertheless, it can be appreciated that any combination of “active”antennas and “scanner” antennas may be used. For instance, a 4×4 MIMOmay use two antennas for providing Wi-Fi and two antennas for scanningand reporting, assuming that certain factors are considered, such ase.g., number of customers or connections to serve, or whether sufficientcomputing resources are available to handle the desired operations.

In another embodiment, the background scanner may establish temporaryconnections to one or more client devices and obtain network-relatedinformation, e.g., SSIDs that are seen by the client devices, signalstrengths related thereto. The background scanner does not provideservice to the client devices; rather, the connection is onlyestablished to monitor network statistics through the client devices; ineffect, the clients are mobile proxies for the scanner(s) 214. Thisnon-service data communication may be utilized in addition to detectingRF signals and related data via the antennas and/or transceivers of thescanner itself, as previously described. However, in some variants, thebackground scanner may also provide network service; e.g., if thescanner is a “repurposed” wireless AP, it may be sufficiently equippedto provide Wi-Fi service. For example, in one implementation,computerized logic on the AP/scanner may invoke the background scannerto function as a Wi-Fi AP (or vice versa), e.g., such as when the CC 210determines that expanding the Wi-Fi service range will enhance servicefor a threshold number of client devices within a given area, andaccordingly transmits a message to the AP/scanner (e.g., via its wiredor wireline backhaul) to cause the mode change.

In various implementations, data or collections of data (e.g., reports)may be sent periodically, at predetermined times (e.g., determined bythe CC 210, CM provisioning server 201, or the scanner itself), atrandom times, at times dynamically determined based on networkconditions, or as needed (e.g., based on a “pull” received from the CC210 or other entity). For example, if the background scanner 214 doesnot detect a coexisting RAT (e.g., only detects Wi-Fi), then it maydetermine that there is no need for a frequent (or any) report to the CC210. That is, the background scanner may send no data or report, andschedule a confirmatory scan at a later time as determined automatically(e.g., algorithmically, or based on historical or statisticalcalculations) by logic within the scanner or the CC 210. If a subsequentscan detects no competing RAT, then the scan interval may be “backedoff” or otherwise modified. Alternatively or in addition, the data orreport from a given scan or set of scans may be scheduled fortransmission at a future time, such as after aggregation of enough datafor the CC 210 to conduct sufficient analysis.

In some implementations, the CC 210 may be in a localized controllerthat resides in the AP 204, 206, or within the background scanner(s)214, or may have components or processes distributed in each (in effectforming a “virtual” controller). In other implementations, the CC 210may be located within the venue but separate from the AP/scanner(s), orwithin an intermediate network entity, e.g., the aforementioned datacenter or other portion of the MSO infrastructure as shown in FIGS. 2-2a. Such a localized location for the CC 210 may in some cases improvecommunication with the background scanner 214; for example, there may belower latency with respect to receiving frequent reports from thebackground scanner 214 and corresponding acknowledgement from the localCC. Communication with Wi-Fi APs 204, 206) may also be similarlyenhanced; e.g., for pushing updates or configuration change data to theAPs.

When the CC 210 receives a report from the background scanner(s) 214,the CC 210 (and/or other entities with the infrastructure such as theprovisioning server 201 if so configured) is then able to perform, interalia, radio resource management (RRM) procedures. In one implementation,such RRM procedures include algorithmic analysis of the data collectedby the background scanner(s) 214 in order to characterize the RFenvironment within which the APs 204, 206 served by the CC 210 operate,and ultimately modify the configuration of the WLAN modem(s) thereof ifneeded. Such characterization may include assessment of data relating toany number of parameters, including specific measures of link qualitysuch as, without limitation: received signal strength (RSS/RSSI),signal-to-noise ratio (SNR), carrier-to-noise ratio (CNR),signal-to-interference plus noise ratio (SINR), carrier-to-interferenceplus noise ratio (CINR), bit error rate (BER), block error rate (BLER),packet error rate (PER), etc., depending on the capabilities of thescanner 214 itself. For example, where the scanner 216 is moresimplified and merely measures RF parametric data, it may not havesufficient capability to measure BER/BLER/PER, since it is transactingno client data. Alternatively, more capable scanner configurations(e.g., where the scanner 214 also functions as an AP) may be able toprovide more comprehensive statistics.

Referring back to the exemplary embodiment as shown in FIG. 2, the CC210 is configured to send instructions and/or data (e.g., configurationfiles) to Wi-Fi APs 202, 204, 206, 208 in the network based at least onreports received from the scanner(s) 214, 216, 218. Instructions or datamay be delivered through existing infrastructure that provides datacommunication between APs and the backend, including wired and/orwireless means. For example, each scanner is configured to (i) receivedata, including commands, from the coexistence controller 210 or otherentity, and (ii) collect and upload monitoring statistics or otherrelevant data to the controller 210, each of (i) and (ii) which mayoccur via a wired or wireless link. For example, the sensors may includeCAT-5/6 network capability (e.g., via an Ethernet or similar PHY), oralternatively may use a short-or-moderate range wireless link such asBluetooth, ZigBee, or even Wi-Fi.

Moreover, the “zero-IT” provisioning connection manager (CM) server 201,which is also in the backend and/or in another centralized managedlocation of the MSO network as shown in FIG. 2, may store aconfiguration file (e.g., an autoconfig file) associated with variousclients, such as in the client database 203 (FIG. 2). It may also accessthe AP DB 205 regarding AP configuration data. In one embodiment, aconfiguration file for a client 211, 212, 213 may be retrieved by the CMprovisioning server 201, modified per the data/reports and informationreceived from the CC 210 (or even the background scanner(s) 214, 216,218 directly), and pushed to the CM 221 of the clients respectively. Inone variant, the CM provisioning server analyzes the data of the reportsbefore transferring a configuration file to the clients indicating whichparameters are to be modified. In one embodiment, the logicalcommunication between the protocol stack of the CM 221 and that of theprovisioning server 201 software (shown as dotted lines 250 on FIG. 2)is physically effected via any relevant PHY or medium between the clientand the provisioning server 201, including for example: (i) via the WLANcommunications between the CC 210 and the clients (e.g., via a downlinkfrom the CC to each client for installation); (ii) via an LTE or othercellular data link of the client (e.g., as sent by the MSO via SMS orother means, whereby the receiving client can access a URL via the LTEdata interface); (iii) via a PAN interface of sufficient bandwidth(e.g., EDR Bluetooth or the like), or via yet other means.

As an aside, downloadable application or “app” may be available toclient devices of subscribers of an MSO or cable network (and/or thegeneral public), where the app allows users to connect to or obtainMSO-provided services. Application program interfaces (APIs) may beincluded in an MSO-provided applications, installed with otherproprietary software that comes prepackaged with the client device, ornatively available on the CC or other controller apparatus. Such APIsmay include common network protocols or programming languages configuredto enable communication with other network entities as well as receiptand transmit signals that may be interpreted by a receiving device(e.g., client device).

In one implementation, the changes to the client WLAN interfacetransmitted via the configuration data (file) may include alteration ofthe client WLAN transmission and/or reception characteristics, such astransmit power level, energy detect (ED) threshold level, beamformparameters (e.g., modification of phase and/or amplitude of transmittersignal), use of one or more antennas, etc., thereby making Wi-Fi a moreviable connection option, e.g., for these client devices, such as whenon the edge of the Wi-Fi network where a minimal signal strength ofapproximately −80 dBm or lower may occur. For example, the settings onthe client device may be modified by the configuration data transmittedto the CM 221 so as to make the client device more receptive to certainRATs, i.e., the client device may consider a weak Wi-Fi signal (e.g., at−80 dBm) a viable connection despite the existence of a coexistingnetwork. Accordingly, the modified transmit characteristics allow clientdevices within range of the AP and/or users of the client devices to“see” a Wi-Fi AP that may not have been detectable otherwise in acoexistence scenario with LTE (e.g., a service set identifier (SSID) maynow appear in a list of available networks).

Likewise, the APs 202, 204, 206, 208 may receive their relevantconfiguration data (e.g., modified configuration file) from the CC 210directly via the respective AP backhaul(s), and apply changes to itstransmission and/or reception characteristics, such as transmit powerlevel, energy detect (ED) threshold level, beamform parameters (e.g.,modification of phase and/or amplitude of transmitter signal), physicalconfiguration of one or more antennas at the AP (e.g., angle ofantennas, relative distance from each other), etc., thereby making theWLAN AP a more viable connection option for the client devices. Theoriginal configurations may be stored at the respective AP 202, 204,206, 208, and/or retrieved from the AP DB 205 (FIG. 2), whether by theCC 210 or the provisioning server 201. In some embodiments, the appliedupdates to the configuration at each AP may persist for a prescribedperiod of time, or until a new update is applied to that AP.

Notably, in one variant, the AP DB 205 also is configured to containdata obtained by the scanner(s) (and/or APs functioning as scanners) inorder to characterize the particular venue or premises in terms ofelectromagnetic environment. For example, the DB 205 may include tabularor other data reflecting the strength of in-band (e.g., 2.4 or 5.0 GHz)emitters, their persistence, variation as a function of time, and evenazimuthal or spatial variation. In this fashion, changes in the venue orpremises environment may be detected (e.g., by comparing a venue profiletaken currently with a historical one for that same venue), andcorrelated to e.g., events of interest being held within the venue.Moreover, such data can be useful in predicting the effects ofconfiguration changes within the venue, whether due to AP/scannerplacement, additional user devices, physical changes to the venue, etc.See, e.g., co-owned U.S. patent application Ser. No. 15/612,630 filedJun. 2, 2017 entitled “APPARATUS AND METHODS FOR PROVIDING WIRELESSSERVICE IN A VENUE,” and issued as U.S. Pat. No. 10,645,547 on May 5,2020, incorporated herein by reference in its entirety, for exemplaryuses of such data.

Exemplary Operation

Based on the foregoing architecture 200 of FIG. 2, an exemplary processfor controlling multiple coexisting wireless networks according to thepresent disclosure will now be described in the context of FIG. 4.

In one exemplary scenario, both Wi-Fi and LTE (e.g., LTE-U and/orLTE-LAA) are deployed within a venue (e.g., airport, shopping mall,stadium, hospital, concert hall, or other commercial buildings). Wi-Fiis served by at least one Wi-Fi access point 202, 204, 206, 208maintained by the service provider/network operator, which also operatesCC 210 and CM provisioning server 201. The APs are able to reach clientdevices 211, e.g., those within range of a service area 414. LTE isserved by a neighboring node 408 (e.g., a base station, small cell,etc.) in or proximate to the same venue. The LTE node 408 provides LTE-Uand/or LTE-LAA connectivity to the venue. More directly, LTE-U and/orLTE-LAA may operate in the same frequency band as typical Wi-Ficonnections (e.g., 5 GHz band or other unlicensed band), causing“collision” with regular Wi-Fi signals. As discussed supra, the clientdevice may prioritize a connection to the LTE node 408 depending on thehardware configuration or software setting of the cell tower and/or theclient device itself. Nonetheless, client devices 211 are capable ofwirelessly accessing a network via the AP(s) and the cell tower 408 onthe same channel (pending resolution of the competition for the medium).

The dedicated background scanner 214 detects the presence of Wi-Fi andLTE-U and/or LTE-LAA (collectively “LTE” for the purposes of thisexemplary operation) operating in the same channel. The backgroundscanner 214 may also report statistics related to usage of one or morechannels, number of client devices, number of RATs, types of RATs,congestion level and/or other relevant information. The backgroundscanner transmits this information to the CC 210, e.g., in one or moredata messages or structures (e.g., report files).

To mitigate the effect of collision between the detected RATs (i.e.,Wi-Fi and LTE), the CC 210 determines that the configuration of one ormore Wi-Fi APs (e.g., AP 204 in FIG. 4) should be updated so as to meeta prescribed performance level; e.g., to match the LTE in connectivityparameters (such as back-off waiting period, LBT procedures, signalstrength, RF parameters, etc.), thereby affording Wi-Fi a morecompetitive opportunity to connect with the client devices 211.

To update the configuration of the Wi-Fi AP 204, the CC 210 retrieves aconfiguration file (e.g., an “autoconfig” file) from the AP DB 205. TheCC 210 adjusts the necessary parameters in the configuration file (e.g.,connectivity parameters as described elsewhere herein) according to thereport data received from the background scanner 214; notably, suchadjustment or alteration can be conducted algorithmically; i.e., by acomputerized logic operative on the CC 210. For instance, the exemplarylogical flow implemented by the CC 210 in modifying an AP configurationas described with respect to FIGS. 5-5 b herein can be used inselectively altering the AP configuration.

After modification, the CC 210 sends the adjusted configuration file tothe Wi-Fi AP 204. As long as the adjusted configuration file is ineffect at the AP, any client devices 211 within the service range 414may experience enhanced connectivity to the Wi-Fi, including a greatersignal strength, more robust connection, uninterrupted connections,etc., even when competing with the LTE RAT.

Additionally, the network (e.g., the provisioning server 201, or eventhe CC 210 at direction of the provisioning server 201 and via therelevant AP 204) may push various settings by, e.g., interfacing with asoftware application (i.e., mobile “app”) to allow the client device to,e.g., lower an ED (energy detect) threshold so as to preventde-prioritization of Wi-Fi services by the client's connection managerprocess. For instance, the client may be instructed to lower its the EDthreshold for Wi-Fi to −80 dBm (e.g., from −73 dBm), while keeping thethreshold for LTE the same. This selective adjustment allows the clientdevice (and/or its user, such as via UI presented by the connectionmanager) to consider either a Wi-Fi connection—e.g., consider an SSIDfor the AP 204 as “visible” or eligible for connection to the device—aswell as to use “data” to connect to LTE (as opposed to LTE being theonly option). This software-based adjustment may be especially viablefor customers of the MSO or network service provider providing the Wi-Fiservice, such customers who may already enjoy various features of themobile application provided by the MSO/provider which are not accessiblevia the LTE data interface.

However, in the exemplary implementation, the client device is not inany way precluded from or incapable of connecting to the LTE network. Byadjusting the connectivity parameters of the Wi-Fi AP (and/or the clientitself), such client devices may not disfavor Wi-Fi by virtue of, e.g.,being on the edge of the Wi-Fi network range (e.g., near the dotted lineof service area 414), but also may utilize LTE or other RATs when thelatter is clearly the better choice.

Methods—

Various methods and embodiments thereof for controlling wirelessnetworks according to the present disclosure are now described withrespect to FIGS. 5-6.

FIG. 5 illustrates an exemplary embodiment of a method 500 implementedby the system architecture (e.g., the system 200 as discussed above withrespect to FIG. 2) to enable connectivity to a wireless network (e.g.,Wi-Fi network) by a client device in a coexistence environment. Thewireless network useful with method 500 is not limited to those embodiedin FIGS. 2, 4 and 5 herein, and may be used with any wireless-enabledclient device and any architecture utilizing data communication amongnodes (especially those with multiple coexisting networks).

At step 502, the CC (e.g., CC 210 of FIG. 2) or other network entitydetermines whether multiple coexisting radio access technologies (RATs)are present within a venue served by the CC 210. In an exemplaryembodiment, the CC may determine a coexistence scenario by receiving areport from a background scanner (e.g., scanner 214 of FIG. 4) by wiredor wireless data connection, where the report indicates that the scannerhas detected two or more RATs operating in the same frequency bandand/or channel(s) (e.g., Wi-Fi and LTE-U and/or LTE-LAA operating in the5.0 GHz band).

In its simplest form, the detection of one or more co-existing RATs maybe accomplished merely by receiving RF signals in a prescribed frequencyband of sufficient strength (e.g., >N dBm in a band centered at 5.0GHz+/−5 MHz), such as via an integration function which determines thearea under the energy curve in that band (and hence the “intensity” ofthe possible interfering signal, thereby differentiating it from saybackground or spurious noise). Stated differently, the presence of asufficiently intense RF signal in the particular band can be consideredde facto evidence of the presence of a prescribed RAT technology. Suchmeasurements can also utilize a temporal or persistence aspect; e.g.,integrated over time, or repetitive instances within a prescribed periodof time, such as would indicate a definitive downlink (DL) signal from abase station (e.g., eNodeB) or other RAT component.

Alternatively, the scanner logic (or that of another analytical entity,such as the CC 210 or server 201) can utilize more sophisticatedtechniques for RAT detection and identification. For example, it can beassumed that in an exemplary LTE-based installation, the DL (from basestation to mobile) would be the primary interferer, based on itssignificantly higher radiated power as compared to the handset(s) on theUL. Hence, in one variant, the CC 210 (or other processing entity suchas the server 201) can access the AP/environment database 205 (FIG. 2)to obtain historical data relating to exemplary LTE interferenceprofiles; for example a Signal-to-Interference Noise Ratio (SINR) withina prescribed range (e.g., >23 dB to −2.5 dB), and/or a Reference SignalReceived Power (RSRP) within a given range (e.g., −70 dBm to −120 dBm).

SINR is defined by Eqn. (1) below:SINR=S/(I+N)  (1)where:

-   -   S is the power of measured usable signals, such as reference        signals (RS) and physical downlink shared channels (PDSCHs);    -   I is the average interference power; the power of measured        signals or channel interference signals from e.g., other cells;        and    -   N is background noise, which can be correlated to measurement        bandwidth and receiver noise coefficient(s).

In Eqn. (1), all quantities are generally measured over the samefrequency bandwidth and normalized to one sub-carrier bandwidth. SINR isgenerally used as a measure of signal quality (and data throughput), butit is not defined in the 3GPP standards (and hence is not required to bereported to the network infrastructure; however, UE's (mobile devices inthe LTE network) typically use SINR to calculate the CQI (ChannelQuality Indicator) which they do report to the network.

RSRP is defined, per 3GPP, as the linear average over the powercontributions (in W) of the resource elements (REs) that carrycell-specific reference signals within the considered measurementfrequency bandwidth. The reference point for the RSRP determination isthe antenna connector of the UE.

RSRP measurement, normally expressed in dBm, is utilized for rankingdifferent candidate cells in accordance with their perceived signalstrength.

Hence, by analogy, SINR and/or RSRP can be determined by the scanner(s)214, obtaining RSRP measurements for any (one or more) interfering basestations within the scanner range. With SINR/RSRP values within theprescribed ranges, the presence of one or more LTE base stations can beat least assumed.

Alternatively (or in conjunction with the foregoing), Received SignalStrength Index (RSSI) and/or Reference Signal Received Quality (RSRQ)may be utilized for LTE interferer detection. RSRQ is another signalquality metric, considering also RSSI and the number of used ResourceBlocks (N); specifically:RSRQ=(N*RSRP)/RSSI(measured over the same bandwidth)  (2)

RSSI is a measure of the average total received power observed only inOFDM symbols containing reference symbols for antenna port 0 (e.g., OFDMsymbol 0 and 4 in a slot) in the measurement bandwidth over N resourceblocks.

It is noted that the total received power of the carrier RSSI includesthe power from common channel serving and non-serving cells, adjacentchannel interference, thermal noise, and other sources. Hence, it isless specific than the above-described metrics.

Hence, in one implementation, one or more of the foregoing parametersare measured by the scanner(s) 214 in the region or venue of interest,within the target frequency band (e.g., in or around 5 GHz), and thesevalues are compared to historical data within the database andreflective of an operating LTE system (such as for example at a priortime when an LTE base station was communicating with a prescribed oreven indeterminate number of LTE UE's). As noted above, the historicaldata may also be represented as one or more parametric ranges, such thatif the measured signals have values falling within the historicalranges, the presence of an LTE interferer is assumed.

While the foregoing techniques can generally reliably detect LTEinterferers which may interfere with the WLAN client interface(s), thepresent disclosure contemplates yet further mechanisms which may beemployed to definitively identify and/or characterize the interferer(s)as being LTE-based. Specifically, in one embodiment, the scanner(s) 214(and/or the processing network entity or entities such as the CC 210and/or the provisioning server 201) include an LTE emulator module 813(FIG. 8) and analytical logic which may be rendered for example as aseparate RF receiver with LTE-capable firmware, or as part of the extantscanner radio. In operation, the LTE emulator module is configured toreceive and decode one or more “public” resource or broadcast channelstransmitted by e.g., the interfering LTE base station(s). As is known,LTE systems utilize OFDM on their DL (base to UE), and SC-FDMA on theirUL (UE to base), and further employ a number of shared/control channelsfor a variety of control, signaling, and other functions. These channelsexist in both DL and

UL directions, and include the: (i) physical downlink control channel(PDCCH); (ii) physical uplink control channel (PUCCH); (iii) physicaldownlink shared channel (PDSCH); and (iv) physical uplink shared channel(PUSCH). These channels can be decoded by a receiver such as theemulator module to definitely determine that a prescribed interferer inthe frequency band(s) of interest is in fact LTE-based.

In operation, the LTE UE will report its CSI (channel state information,including CQI or channel quality index) via one of the UL channels;i.e., PUSCH or PUCCH, thereby characterizing the RF receivingenvironment for each reporting UE. The eNodeB takes the reported CSIinformation to develop a schedule for transmission to the UE(s) via thePDSCH, and DL resource allocation is made via the PDCCH. UL grants (forUE traffic operations such as when no PUSCH is available) are also madeby the eNodeB via the PDCCH, based on requests sent via the PUCCH.

Table 1 below illustrates a hypothetical DL Link Budget (i.e., base toUE) for a data rate of 1 Mbps with dual-antenna receiver, in anexemplary frequency band (2.4 GHz):

TABLE 1 Data rate (Mbps) 1 Transmitter - eNode B a PDSCH power (dBm)46.0 b TX antenna gain (dBi) 18.0 c Cable loss (dB) 1.0 d EIRP (dBm)61.0 = a + b + c Receiver - UE e UE noise figure (dB) 7.0 f Thermalnoise (dBm) — 104.5 = k(Boltzmann) * T(290K) * B(360 kHz) g Receivernoise floor −97.5 = e + f (dBm) h SINR (dB) −10.0 (e.g., from scanner214) i Receiver sensitivity −107.5 = g + h (dBm) j Interference Margin3.0 (dB) k Control Channel 1.0 Overhead (dB) l RX antenna gain (dBi) 0.0m Body Loss (dB) 0.0 Maximum path loss 164.5 dB (= d − i − j − k + l −m)

In this case, roughly 165 dB of loss can be sustained in the linkbetween the transmitter (eNodeB) and the receiver (UE). Actualrepresentative values for the aforementioned reference and controlchannels are shown in Table 2:

TABLE 2 MAPL (Link Budget) in MAPL (Link Budget) in Channel dB; zerosector loading dB; 50% sector loading PDCCH 158 155 PUCCH 158 155 PDSCH156 151 PUSCH 148 145

Hence, in one embodiment, the aforementioned values (or similar) arestored in the environmental DB 205 (FIG. 2); when a suitableSINR/RSRP/RSRQ value is detected in the frequency band of interest bythe scanner(s) 214 as described above, this data is sent by thescanner(s) to the CC 210 for further analysis, including accessing theaforementioned LTE DL (and UL if appropriate) signals to attempt todecode the appropriate communications on the detected broadcastchannel(s). Note that the decode operations can be conducted by thescanner(s) themselves prior to obtaining any resource allocations (andhence without registration to the LTE network), depending on theirfirmware configuration and how the emulator module is implemented withinthe particular installation. Hence, the LTE emulator 813 (FIG. 8) of theexemplary embodiment advantageously need not be able to register withthe interfering network, or have any data on the identity of thenetwork, its operator, etc.

In one variant, the CC 210 is configured to, based on the MAPL values ofTable 2 above (which are e.g., stored in the DB 205), determine one ormore adjustments to the WLAN AP(s). For example, in one implementation,the measured SINR value from the scanner(s) 214 is used in an algorithm(such as reflected in Table 1) to, based on assumed values of thermalnoise floor of the receiving scanner, scanner receiving antenna gain,zero body loss, etc., “back out” the requisite WLAN Tx power required toincrease the power received at the receiving client device WLAN receiverchain to be, for instance, roughly comparable to the corresponding LTEsignal (i.e., from the eNodeB), thereby ostensibly maintaining the WLANinterface “competitive” to the LTE interface.

For example (see Table 3), if the PDSCH zero sector loading MAPL is 156dB (Table 2), and the DL Inference Margin (IM) is on the order of <5 dB,and an assumed SINR of −8.0 dB, etc., then the PDSCH transmit power canbe calculated as follows:

TABLE 3 Data rate (Mbps) 1 Transmitter - eNode B a PDSCH power (dBm)46.0 b TX antenna gain (dBi) 18.0 c Cable loss (dB) 1.0 d EIRP (dBm)61.0 = a + b + c Receiver - Scanner e UE noise figure (dB) 7.0 f Thermalnoise (dBm) — 104.5 = k(Boltzmann) * T(290K) * B(360 kHz) g Receivernoise floor −97.5 = e + f (dBm) h SINR (dB) −8.0 i Receiver sensitivity−105.5 = g + h (dBm) j Interference Margin 3.0 (dB) k Control Channel1.0 Overhead (dB) l RX antenna gain (dBi) 0.0 m Body Loss (dB) 0.0Maximum path loss 156 dB (= d − i − j − k + l − m)Tx eNodeB PDSCH power=156 dB−105.5−3.0−1.0+0.0−0.0−18.0−1.0=27.5 dB.

As will be recognized, more Tx power is not always better; specifically,there comes a point when a WLAN AP may, inter alia, interfere with otherWLAN APs in the same venue, and/or the user (client) device receivers.Hence, exemplary embodiments of the present disclosure advantageouslycalculate a Tx power level for the affected APs utilizing themethodology above, and insert this configuration change, as opposed tomerely increasing the Tx power by e.g., prescribed increments.Notwithstanding, the present disclosure also contemplates use of a“feedback loop,” such as where the AP Tx is incrementally increased, andthe effect on data rate or other performance metric evaluated todetermine the efficacy of the increase (or other modification to e.g.,the transmitter chain of the AP, and/or receiver chain of the clientdevice). See also discussion of steps 590 and 592 of FIG. 5b providedinfra.

It will also be appreciated that in the exemplary implementations, someassumptions regarding the source of LTE-based interference are made inorder to simplify the protocol(s) employed by the CC 210 when performingthe methods described herein. Specifically, as is known, transmitted RFpower from a (presumed) point source falls of generally as 1/R², whereR=distance from the transmitter. In that eNodeB base stations aregenerally not electrically power constrained and must cover relativelylarge geographical areas to provide service to customers, the transmitpower (e.g., EIRP) of the eNodeB is typically many times higher than acorresponding UE transmitter at the same range. Accordingly, it isassumed in the exemplary implementation that the eNodeB(s) will be theinterferer(s) of concern, with the UEs adding only marginally to thateffect. However, it is also recognized that the UE may, as part of itsUL communications, radiate at a location immediately proximate to thescanner and/or AP of interest, thereby making the UE an effectiveinterferer due to its minimal 1/R² losses in the small distance betweenitself and the scanner/AP. Hence, in another implementation of themethodology, calculations similar to those for the LTE broadcast DLchannels are performed for the UL channels, and used as part of the WLANAP Tx power configuration. For example, it can be assumed a “worst case”scenario exists when the interfering UE is located directly proximatethe WLAN client (e.g., a person standing next to the WLAN user isutilizing their LTE handset in the 5.0 GHz band). With an assumed MAPLof 148 dB for the PUSCH (Table 2), and knowing the measured SINR fromthe scanner 214, the maximum UE Tx UL power can be determined (usingsimilar assumptions to those above), and the WLAN AP Tx adjustment setaccordingly (i.e., to at least achieve parity with the greater of (i)the eNobeB Tx power, and (ii) the UE Tx power).

It is also recognized that UL/DL asymmetry typically exists; i.e., LTEUE users will be utilizing the DL much more than the UL (largely becauseLTE is a data service, and users of data services tend to download datamore than upload/send it). Hence, the methodologies described herein canmake use of this fact; e.g., whether by assumption, averaging (e.g.,measurement at a number of different times, and presumptively most ofwhich will be representative of DL activity), or active “avoidance”measures such as affirmatively determining when the UE/eNodeB areinvolved in a DL versus UL transaction).

The scanner data may include, inter alia, how many RATs are present,which RATs are present, which frequency bands or channels are occupied,number of client devices in the area, signal strengths, congestionlevels, noise (e.g., signal-to-noise ratio), etc. Alternatively, thescanner data may merely be unprocessed data that is then processed bythe CC 210 (or its designated processing proxy such as the CM server201) to identify the existence of the other RAT(s). It is also notedthat the scanner(s) 214 (and/or the system 200 generally) may beconfigured to, depending on which of the approaches described above areused in a particular implementation, differentiate between: (i) certaintypes of RATs (e.g., LTE, which is an OFDM-based system (downlink) andSC-FDMA on uplink and which uses multiple time and frequency assets suchas multiple sub-carriers and time slots, versus say a CDMA/DSSS-basedRAT such as WCDMA which utilizes spreading codes to distribute itsenergy across say a 5 MHz band); and (ii) between RAT and non-RATsources within a given band (e.g., a cordless telephone or microwaveoven and an LTE or CDMA system).

Moreover, such differentiation can be used as the basis for determiningwhat particular contention management actions (if any) to take under avariety of different scenarios. For example, in one variant, failure todetect an OFDM or CDMA or FHSS type of waveform/modulation/spectralaccess scheme may by default be considered to be a spurious ornon-contentious interferer, such as a microwave oven, leakage fromnearby high-power electrical or other equipment, etc. Conversely,identification of a particular spectral access or modulation schemeknown to be associated with only certain classes of RATs (e.g., FHSSused in Bluetooth PAN interfaces) can enable determination of thecontention management actions necessary; in the case of PANs, nothingmay need to be done, since their transmit power is generally very lowrelative to WLAN. Alternatively, for presumed spurious signals, a shortterm correction or modification may be implemented; e.g., temporary EDreduction, Tx power increase, migration to another band, etc.

Additionally, when the temporal aspects of the signal show onlyintermittent presence, such data may be used to divine the prospectivesource(s). For instance, in a crowded venue, many people are presumed tocarry (and utilize) LTE-based phones, by which data communications canbe conducted. Hence, if the scan of the venue indicates only a veryintermittent single 2.4 GHz interferer (or small group of interferers),this is likely not due to a competing LTE-based RAT, and may in fact bedue to a non-RAT source (or at least a RAT with insufficient RF transmitpower to significantly impede WLAN negotiation and service, such as aBluetooth link to a user's headset or a cordless phone).

It is further noted that the CM server 201 or proxy entity may make thedetermination of the existence/classification of the other RATs (asopposed to the CC or scanner), and merely inform the relevant AP(s) thata co-existence scenario does in fact exist.

Returning again to the method 500 of FIG. 5, if a coexistence scenariois not detected, Wi-Fi access points in the venue may continue operatingnormally. If coexistence is detected at step 502, a multi-RAT“competition management” procedure begins at step 504.

At step 504, the CC may request and receive a configuration file (e.g.,an “autoconfig” file) associated with one or more Wi-Fi access pointsfrom the provisioning server 201 or other entity (such as from the APdatabase 205 directly). The one or more Wi-Fi APs to be modified underthe competition management plan may include all detected APs in aparticular venue; for example, the background scanner may see SSIDsassociated with APs that are detected in the venue over a given periodof time. In other embodiments, the Wi-Fi APs to tune be identified basedon which ones the background scanner has detected, or based on APs knownto the CC 210.

At step 506, the CC modifies one or more connectivity parameters withinthe configuration file for each of the Wi-Fi APs identified in step 504as discussed previously herein.

In one embodiment, the configuration data modification may dictate thattransmit power of the Wi-Fi AP be increased. For example, the typical 20dBm Wi-Fi transmit power may be increased to 30 dBm (or according to anyapplicable regulations), e.g., via “iwconfig” commands. Increasedtransmit power may increase the range of service of the AP and/orimprove the signal strength received by a client device above that ofLTE. A increased transmit power may enhance the battery life of clientdevices as well: By increasing Wi-Fi signal strength, the client device(or its user) may prefer to connect via Wi-Fi rather than a morepower-intensive LTE connection. In another embodiment, the configurationdata modification may instruct the transmit power of the AP to bereduced. A reduced transmit power may conserve power consumption of theAP, which may be useful for APs that are battery powered, usedrelatively infrequently, or typically used by client devices that arewithin close range (a café setting, lounge area, gift shop, smalloffice, concession stand, airport gate, etc.), so as to inter alia,mitigate interference with other RATs (whether operated by the MSO orotherwise), reduce EMI exposure of patrons within the venue, or extendcomponent lifetime (e.g., the longevity of the AP RF transmit chain mayvary as a function of transmit power).

In one variant, the CC 210 may include data or instructions (e.g., in aconfiguration file sent to the AP(s) being modified) to dynamicallyadjust the transmit power based on distance to client devices. In oneimplementation thereof, to measure the distance, the AP may emit one ormore beacons that may be received by a client device, and the clientdevice may send back a response to the AP. The client may determinewhich AP to respond to based on, e.g., a bit-stuffed SSID within thebeacons as described in co-owned U.S. patent application Ser. No.15/063,314 filed Mar. 7, 2016 entitled “APPARATUS AND METHODS FORDYNAMIC OPEN-ACCESS NETWORKS”, and issued as U.S. Pat. No. 10,492,034 onNov. 26, 2019, incorporated by reference supra. In another embodiment,the configuration file data may cause the Wi-Fi AP (or the clientdevice, as discussed below) to communicate on a different frequencyrange allowed for IEEE 802.11 protocols. For example, instead ofenforcing a connection over the 5 GHz spectrum, others such as 2.4 GHzor 3.6 GHz may be allowed. In some variants, the modified configurationfile may contain instructions for switching to an explicit frequency orfrequencies, or instructions to switch automatically as needed (e.g.,based on congestion level or other network conditions), cycledperiodically or on a schedule, or based on some other algorithm. Thismodification allows Wi-Fi users to, at least temporarily, sidestep otherRATs that may be operating in one congested frequency band.

In another embodiment, the configuration file may cause a Wi-Fi AP toenable or disable one or more of its antennas. For example, by enablingan additional antenna, the AP may reach additional users. Disabling anantenna may allow the Wi-Fi AP to qualify and serve only users who arenear the AP and possibly out of service range of other RATs.

At step 508, the CC transmits the modified configuration data to theappropriate Wi-Fi AP(s). At step 510, the CC causes implementation, bythe Wi-Fi AP, of the modified configuration data. Instructions to modifythe parameters at the AP may be executed by a processor apparatusresiding on the AP. At step 512, the method 500 then utilizes one ormore performance assessment techniques to evaluate the performance ofthe AP(s) and/or prevailing RF environment in the venue afterimplementing the AP configuration change(s). In one variant, thescanner(s) 214 is/are used to collect additional parametric datarelating to the frequency bands of interest within the venue, so as topermit e.g., relative comparison of the various RATs under the new APtransmit profiles (or other changes). Alternatively (or in conjunctionwith scanning), the performance of the APs may be assessed viaparametric data relating to actual data sessions such as BER/PER, datathroughput rate, frequency of dropped connections, etc.

Per step 514, the system 200 will determine that either (i) themodifications to the relevant AP(s) in the venue were sufficient toprovide the desired level of performance, or (ii) the modifications werenot sufficient. Note that within steps 510 through 514 of the method500, multiple iterations or loops may occur, such as where individualparameters are modified successively in an incremental fashion, and theperformance subsequently assessed, and/or where different parameters aremodified on subsequent iterations (and performance subsequentlyassessed).

In the event that steps 510-514 do not produce a sufficient level ofperformance, the method 500 then continues to step 516, wheremodifications to the client device(s) 211, 212, 213 can be made,presuming they are configured to do so (i.e., via presence of theaforementioned connection manager (CM) app 221 or other capabilitywithin their indigenous OS or WLAN modem). In one embodiment, theprovisioning server 201 (or even the Wi-Fi AP to which the client isconnected) may instruct a given client device to lower the threshold fordetecting and connecting to Wi-Fi. For example, the Wi-Fi threshold maybe reduced from −72 dBm to −80 dBm in order to be competitive with oneor more other RATs in the venue using the same frequency and/or channels(e.g., LTE-U or LTE-LAA). In one variant, pre-coded configuration filesare resident on the client with CM app 221, such that certain prescribedscenarios can be invoked by the client without having to downloadfurther configuration data; i.e., the provisioning server 201 orinstructing AP 204 may simply communicate to the client that it shouldimplement a particular scenario or configuration file, at which pointthe client indigenously alters its configuration based on the pre-codeddata. In one variant, the (re)configuration data may instruct the clientdevice to reduce the ED threshold yet further down (e.g., from −72 dBmto −85 dBm). One advantage of this type of modification such that theclient device will even more aggressively prefer Wi-Fi over other RATs(e.g., LTE-U, LTE-LAA). However, it may also see degraded connectionquality and other performance issues associated with a weak signal. Inone implementation, a further-lower threshold may be useful with a Wi-FiAP serving a lower coverage area (e.g., used in a small setting, such asa café) and/or using a lower transmit power (e.g., battery-powered AP).

In some embodiments of the exemplary method described above, the CC 210may adjust the connectivity parameters (Wi-Fi ED threshold, AP transmitpower, etc.) irrespective of a coexistence scenario. In other words, theCC may cause a node, e.g., the Wi-Fi AP(s), to maximize its connectivityperformance, or cause a client device to connect to a particular node.In the case of Wi-Fi, providing a likely connection thereto withoutchecking for coexistence may advantageously improve the performance of aclient device (with respect to, e.g., battery consumption and connectionspeed) when the client device is persistently encouraged to connect toWi-Fi, which may result in less consumption of limited battery powerdepending on respective signal strengths of available Wi-Fi and LTEconnections (e.g., by virtue of eliminating the need to switch radiostates in a coexistence scenario, requiring generally less powerconsumption on Wi-Fi relative to LTE, or obviating the need to searchfor either Wi-Fi access points or LTE cell towers). It may furtherresult in less consumption of LTE “data” (subject to, e.g., a quota fromthe LTE service provider).

FIG. 5a illustrates an exemplary implementation of the method 500 ofFIG. 5, in the context of a managed network architecture 200 such asthat of FIG. 2.

As shown in FIG. 5a , the method 520 includes activating the scanner(s)214 per step 522, and configuring them as needed (e.g., for one or morebands of interest) per step 524. Per step 526, the environment in whichthe scanner(s) is/are located is scanned for the parameter(s) ofinterest (e.g., SINR/RSRP/RSRQ), and the measured values compared to oneor more relevant threshold or window criteria, such as those retrievedfrom the DB 205. If the measured values meet the prescribed criteria persteps 528 and 530, then the measured data is then reported to the CC 210per step 532 (because an LTE-based interferer presumptively exists).Based thereon, the CC 210 adjust the Tx power of the one or moreaffected APs per step 534, and subsequently monitors performance for theWLAN system per step 536 to determine its sufficiency. For instance, inone embodiment, the CC 210 obtains data rate and/or error rate data, ordata relating to connection “drops” (ostensibly indicative of faileduser attempts to connect to the WLAN) from the AP over a period of time,and algorithmically assesses whether the inserted configuration changewas effective. If not, follow-on adjustments to the AP (which mayinclude additional power increases, change in MCS, variation in spatialdiversity profile, or other changes), and/or the client (e.g., EDthreshold change via the CM 221) are implemented via step 538.

It will be appreciated that while the scanner(s) 214 is/are shown in theembodiment of FIG. 5a as performing the scanned data threshold/windowanalysis, such analysis may be performed in whole or part by the CC 210or other network entity as well. For example, the scanner(s) may simplyreport the scan results to the CC 210 for analysis thereby.

FIG. 5b shows yet another implementation of the methodology of thedisclosure. As shown in FIG. 5b , the method 540 includes firstactivating the scanner(s) 214 per step 542, and configuring them asneeded (e.g., for one or more bands of interest) per step 544. Per step546, the environment in which the scanner(s) is/are located is scannedfor the parameter(s) of interest (e.g., SINR/RSRP/RSRQ), and themeasured values compared to one or more relevant threshold or windowcriteria, such as those retrieved from the DB 205. If the measuredvalues meet the prescribed criteria per steps 548 and 550, then themeasured data is then reported to the CC 210 per step 552.

At step 554, the CC 210 activates one or more LTE emulator modules 813within the scanner(s) 214 to evaluate the hypothesis that an LTE eNodeB(and/or interfering handset; discussed supra) is active within theservice area 416. In the exemplary embodiment, the CC 210 at steps 554and 556 attempts to establish timing information for the network toestablish that it is in fact an LTE network. For instance, in oneimplementation, the PSS (primary synchronization signal) is detectedusing measurements of RSSI and CAZAC (e.g., Zadoff-Chu sequence)autocorrelation properties, as a UE would normally do when attempting toregister with the network. Specifically, wideband power is measured in aset of prescribed frequency bands, and the bands are ranked based onRSSI magnitude. The Zadoff-Chu sequences are then evaluated in thefrequency domain for a given number of timing hypotheses to determinethe eNodeB's group identity. At this point, the CC 210 can definitelysay that the received signal data is in fact due to an LTE eNodeB pertstep 558.

Next, per steps 560 and 562, the broadcast channel(s) of interest (e.g.,PDSCH) is decoded and evaluated, such as against historical data for LTEeNodeB's maintained within the environmental database 205. While theevaluation of steps 556 and 558 can definitively determine the existenceof an LTE-based emitter, they do not provide sufficient information forevaluation of the relative strength of the emitter(s) as measured at thescanner(s) 214, and hence steps 560 and 562 are used to enable use ofMAPL data as described above to provide an estimate of adjusted Tx powerfor the WLAN AP such that it will at least achieve parity with the LTEeNodeB. For example, in one implementation of steps 560 and 562, themeasured SINR from step 546 is used, as in Table 3 above, to calculatethe estimated eNodeB Tx power given certain assumptions about the eNodeBobtained from the environmental DB 205, including maximum allowed MAPL,DL IM, etc. Consistency with historical data for an eNodeB is also againoptionally evaluated per step 564 (e.g., does the calculated PDSCH Txpower fall within a “realistic” band), and assuming that the scanneddata still qualifies as a valid eNodeB broadcast signal, the APconfiguration data is accessed per step 566, and the coexistencealgorithm of the CC 210 (and/or provisioning server 210, depending onconfiguration) is invoked per step 568.

It is also noted that the selective decode of UL and/or DL broadcastchannels present within the scanned environment can be used as a basisof evaluating different hypotheses of the observed interferer(s). Forinstance, in one implementation, the CC 210 logic is configured to causethe emulator module 813 to attempt to receive and decode both PDSCH andPUSCH channels; the ability to decode one but not the other may provideclues as to the identity of the interferer(s). For example, if the PDSCHdecode is successful, but no PUSCH decode can be completed afterrepeated attempts, then it can be surmised that the interferer is aneNodeB, versus a very close UE.

As part of the coexistence algorithm implementation, the first“correction” within the algorithm hierarchy is implemented per step 570.For example, it may be determined that the most efficient convergence ona desired environment within a target venue is achieved by implementinga first hierarchy template, the latter which may include: (i) firstincrementing the Tx power of the WLAN AP, in a series of prescribedsteps; and (ii) thereafter adjusting one or more additional Txparameters such as spatial diversity/beamforming settings, MCS, etc.,and (iii) thereafter adjusting the ED threshold of the client(s), asrequired, based on the prescribed performance metric (e.g., receivedWLAN link performance data per step 572 such as may be obtained from theAP while transacting data with the client(s)).

Per step 576, the inserted adjustment or configuration change is thenevaluated for a prescribed period of time (which may include adynamically determined period based on lack of client device access ofthe WLAN, since the client may, when confronted with poor WLANperformance, has opted to utilize the LTE data connection for at least aperiod of time), and additional adjustments or changes inserted asneeded based on the selected hierarchy template until the last availablecorrection or change is utilized (step 578), at which point the CC 210generates an error message to the cognizant NMS (network managementserver; not shown) to alert the service provider that the particularvenue or installation is ostensibly being “over-ranged” by the proximateLTE eNodeB(s).

In the illustrated embodiment of FIG. 5b , the method 540 alsooptionally first: (i) re-initializes the participating/affectedscanner(s) 214, since this has no impact on any ongoing datatransactions via the AP(s), per step 586. Once re-initialized, thescanner then scans the environment to determine whether the measuredparameters meet the threshold/window criteria (i.e., is the interferingemitter still active) per step 574, and if so, steps 572 and thereafterare again performed to determine if the WLAN link performance isacceptable (for example, where the scanner was operating improperly ormerely required reboot).

If, on the other hand, the scanner re-initialization does not produceacceptable WLAN link performance then, per step 588, one or more of theaffected APs is/are re-initialized in an attempt to solve the issue.

The illustrated methodology 540 of FIG. 5b also includes a logic “loop”to reduce or back out any inserted configuration changes or adjustmentsif desired. As noted above, more AP Tx power is not always desirable,and in fact can have negative consequences relating to, inter alia,inter-AP or AP/non-associated client interference. Hence, when thepresence of a detected interferer ceases, the methodology 540selectively removes any adjustments that have been entered (e.g., to theAP) via steps 590 and 592. It will be appreciated that the removalalgorithm of step 592 may in fact comprise a sequence or hierarchy suchas that used for insertion of the configuration changes as previouslydescribed, yet effectively in reverse, or can simply constitute ablanket return to the original configuration, depending on the desiredattributes of the particular installation. Yet other schemes will berecognized by those of ordinary skill given the present disclosure, suchas for example: (i) a “wait-and-remove” scheme, wherein theconfiguration changes are removed after certain periods of time haveexpired; (ii) dynamic determination of a removal hierarchy (e.g., wherecertain less-effective configuration changes, as determined by e.g.,data collected during change insertion, can be preferentially removedfirst to as to maintain only necessary changes inserted), and (iii)dynamic sensitivity analysis, such as where the removal of insertedchanges, and subsequent re-insertion thereof, is performed so as todetermine the appropriate hierarchy for removal.

FIG. 6 is a ladder diagram illustrating an exemplary communications flow600 for configuring and controlling Wi-Fi connectivity within a venuewith coexisting Wi-Fi and LTE-U or LTE-LAA services, such as thatpreviously described.

At step 602 a of the exemplary embodiment, a dedicated backgroundscanner 214 sends an RF detection report to a CC 210. The report maycontain information related to, e.g., transmit power of nearby accesspoints and nodes, number of users, channels used, data transmissionrates, beamforming settings, modulation/coding scheme (MCS), or otherstatistics associated with signals propagating within the venue, e.g.,signals related to ongoing or newly established data sessions 604, 606over Wi-Fi and LTE (e.g., LTE-U and/or LTE-LAA). Wi-Fi signals mayoriginate from a Wi-Fi access point 204; LTE signals may come from asmall cell or node (e.g., cell tower 408). As previously discussed, thebackground scanner may be strategically placed to detect signals withina particular venue or area, or scan for signals from known access pointsand nodes in the venue. In this exemplary embodiment, detected datasession 606 corresponds to LTE-U, but other RATs may be detected. TheICC may require more than one report that confirms the presence ofcoexisting RATs (e.g., Wi-Fi and LTE-U). At step 602 b, one suchrepeated detection report may be transmitted to the CC 210.

At step 608, the CC 210 analyzes the report to determine and identifythe presence of RATs (e.g., LTE tower 408 and/or Wi-Fi AP 204) near thebackground scanner 214. In one embodiment, the analysis of the reportmay include a determination of parameters as previously described; e.g.,the strength or quality of the radio signals detected (including, e.g.,signal-to-noise ratio (SNR) and/or received signal strength indicator(RSSI)), frequency spectrum used (e.g., 5 GHz band), energy detection(ED) thresholds, channels used, and/or other connectivity parametersthat indicate the likely choices that a client device may have forwirelessly connecting to a network.

At step 610, based on the analyzed report, the CC 210 determines whetherLTE is present in the venue targeted by the background scanner(s) 214.For example, LTE-U or LTE-LAA operating in the same frequency bandand/or channel(s) as Wi-Fi (e.g., 5 GHz band) may be detected,indicating two or more coexisting RATs. Note that in various otherimplementations, the CC 210 may be configured to detect RATs other thanLTE (e.g., Bluetooth, LTE-A, 3G UMTS, CDMA, EDGE (Enhanced Data Ratesfor GSM Evolution), or 2G USM).

If the CC does not determine that LTE is present at step 610, no actionis taken to adjust network settings, i.e., no collision avoidance orcontention management mechanism is utilized.

If the CC 210 determines the presence of LTE at step 610, data isexchanged between the CC and provisioning server 201, the data beingassociated with the Wi-Fi AP(s) providing Wi-Fi service that coexistswith the detected LTE service, at step 612. More specifically, the CC210 may indicate the coexistence scenario, or which Wi-Fi AP(s) will bemodified, to the CM provisioning server 201, which in turns transmits aconfiguration file for, e.g., Wi-Fi AP 203 to the CC (e.g., via a data“push”). In one variant, the CC may obtain the configuration files forall Wi-Fi APs in the venue that are operated by the CC (or others inwhich it is in communication, such as via sub-net). In oneimplementation, these APs include all APs that the background scannerhas detected signals from (e.g., the scanner may record SSIDs that ithas seen over a period of time). In another variant, the CC mayselectively determine which AP(s) to tune based on coverage areas ofeach AP and LTE nodes that are known to be installed within the venue.

At step 614, the CC identifies the Wi-Fi AP(s) to tune as discussedabove, and modifies one or more connectivity parameters containedtherein, resulting in a modified configuration file (e.g., an“autoconfig” file). The modified parameters may include an increasedtransmit power of one or more antennas or transceivers on an AP, a lowerED threshold for Wi-Fi connectivity, and/or frequency ranges used (e.g.,if LTE-U or LTE-LAA is using the 5 GHz band, then Wi-Fi may move to aless-crowded one of other legal frequencies for IEEE 802.11 protocols,i.e., one or more of 2.4 GHz, 3.6 GHz, 4.9 GHz and 5.9 GHz). Otherconsiderations for a modified Wi-Fi connection may be considered, suchas beamform parameters (e.g., modification of phase and/or amplitude oftransmitter signal), physical configuration of one or more antennas atthe AP (e.g., angle of antennas, relative distance from each other),and/or others.

It will be appreciated that one or a combination of these parameters maybe tuned at a time, and may be modified in the opposite direction asthose noted above such as e.g., for a sensitivity analysis or the like,or yet other reasons. For example, transmit power may be decreased, orED threshold may be raised, so as to determine (via the scanner(s) 214)the effect on actual sensed RF parameters. Moreover, suchcounter-corrections may assure a high-speed Wi-Fi-only “hotspot”, i.e.,an AP in which the service area is of a shorter range, but also may beout of range for LTE service, essentially qualifying users who prefer astronger Wi-Fi signal even if they must be closer to the source (i.e.,the AP). In one variant thereof, transmit power may be lowered based ondistance, i.e., the closer a client device, the lower the transmitpower. An AP may detect the distance from a client device and itself by,e.g., measuring a response time of a beacon sent to the client device,or by other means such as GPS. For an AP that typically servesrelatively few client devices at a time, there is no need to maintain alarge-range signal.

In another variant, power considerations may affect the transmit powerwhen there is a limited availability of power, e.g., for abattery-powered AP or a client device low on battery. That is, if the APis running low on battery, the AP may reduce its transmit power.Conversely, if the AP receives a low-battery indication from the clientdevice, the AP may increase its transmit power so as to increase thelikelihood that the client devices connects to a Wi-Fi signal showinghigher signal strength and avoid use of a comparatively “energy-heavy”LTE interface.

Further with respect to step 614, the AP(s) may detect one or morepotential client devices within the service range of the AP(s), whichmay be assumed to be capable of receiving both Wi-Fi and LTE services.In one embodiment, APs may detect client devices by determining whichdevices are already connected (i.e., by association of a given clientwith a given AP, its location is resolved to at least the effectiverange of the AP). In another embodiment, APs may find client devices bydetecting responses to beacons, probe requests, or other data structuresthat are transmitted therefrom (e.g., broadcast), as described in, e.g.,co-owned and co-pending U.S. patent application Ser. No. 15/063,314filed Mar. 7, 2016 and entitled “APPARATUS AND METHODS FOR DYNAMICOPEN-ACCESS NETWORKS”, incorporated by reference supra.

At step 616, the CC 210 pushes (i.e., transmits) the modifiedconfiguration file to the identified AP(s), by wired or wireless means(e.g., via AP backhaul; see FIG. 2a ). Each AP receiving a modifiedconfiguration file updates its transmit/receive or other settingsaccordingly. The AP may also retain its previous and/or originalconfiguration files within a local or remote storage unit (including theAP database 205), which may be used to revert back to a previous setting(e.g., if Wi-Fi no longer coexists with LTE, based on a determination bythe CC, and/or based on other conditions). By virtue of the updatedsettings, the AP 204 may operate with a higher transmit power or signalstrength. One end result is that the client devices may detect and/ordisplay additional SSIDs from Wi-Fi APs for automatic or manualconnection.

With regard to causing client devices to update (e.g., lower) its EDthreshold, in one embodiment, the provisioning server 201 may optionallysend instructions to client devices within its service range at step618. The instructions may be configured to update client-side softwaresettings, such as ED thresholds for Wi-Fi. For example, the thresholdmay be reduced to match that of LTE (or be lower), e.g., to −80 to −85dBm. In one embodiment, these instructions may be received via the CMapp 221, e.g., a downloadable software application offered by a serviceprovider to its customers or subscribers. The app may include anapplication programming interface (API) available from the serviceprovider operating the AP, and offer various resources that enhance thecustomer experience, e.g., convenient access to billing informationand/or payment options reviewable by customers, exclusive content ormedia from the service provider, online or remote “cloud” storage, emailaccess, interface for shopping for additional hardware or features, oraccess to support and troubleshooting help. For client devices withoutthe software or those who are not current subscribers to the serviceprovider, instructions may be received via bit-stuffed beacons (asdescribed in, e.g., co-owned and co-pending U.S. patent application Ser.No. 15/063,314 filed Mar. 7, 2016 and entitled “APPARATUS AND METHODSFOR DYNAMIC OPEN-ACCESS NETWORKS”, incorporated by reference supra). Inone variant, the network services from the Wi-Fi AP 204 are accessibleonly by MSO-authorized client devices or client devices running thedownloadable app.

The foregoing exemplary flow process may be repeated for each instanceof identifying a multi-RAT environment.

Coexistence Controller (CC) Apparatus—

FIG. 7 illustrates a block diagram of exemplary hardware andarchitecture of a controller apparatus, e.g., the Coexistence Controller(CC) 210 of FIG. 2, useful for operation in accordance with the presentdisclosure.

In one exemplary embodiment as shown, the CC 210 includes, inter alia, aprocessor apparatus or subsystem 702, a program memory module 704, aconnectivity manager module 706 (here implemented as software orfirmware operative to execute on the processor 702), a back-end (e.g.,headend backhaul) network interface 710, and a front-end networkinterface 708 (i.e., AP/scanner local backhaul). Although the exemplarycontroller 210 may be used as described within the present disclosure,those of ordinary skill in the related arts will readily appreciate,given the present disclosure, that the controller apparatus may bevirtualized and/or distributed within other core network entities (thushaving ready access to power for continued operation), and hence theforegoing apparatus 210 is purely illustrative.

More particularly, the exemplary CC apparatus 210 can be physicallylocated near or within the centralized manager network (e.g., MSOnetwork); an intermediate entity, e.g., within a data center, such as anAP controller (see FIG. 2a ); and/or within “cloud” entities or otherportions of the infrastructure of which the rest of the wireless network(as discussed supra) is a part, whether owned/operated by the MSO orotherwise. In some embodiments, the CC 210 may be one of severalcontrollers, each having equivalent effectiveness or different levels ofuse, e.g., within a hierarchy (e.g., the CC 210 may be under a “parent”controller that manages multiple slave or subordinate controllers).

In one embodiment, the processor apparatus 702 may include one or moreof a digital signal processor, microprocessor, field-programmable gatearray, or plurality of processing components mounted on one or moresubstrates. The processor 702 may also comprise an internal cachememory. The processing subsystem is in communication with a programmemory module or subsystem 704, where the latter may include memorywhich may comprise, e.g., SRAM, flash and/or SDRAM components. Thememory module 804 may implement one or more of direct memory access(DMA) type hardware, so as to facilitate data accesses as is well knownin the art. The memory module of the exemplary embodiment contains oneor more computer-executable instructions that are executable by theprocessor apparatus 702. A mass storage device (e.g., HDD or SSD, oreven NAND flash or the like) is also provided as shown.

The processing apparatus 702 is configured to execute at least onecomputer program stored in memory 704 (e.g., the logic of the CCconnectivity manager 706 which implements the various CC functionsdescribed herein with respect to contention management of the WLANdevices relative to other RATs). Other embodiments may implement suchfunctionality within dedicated hardware, logic, and/or specializedco-processors (not shown). For instance, the connectivity managerfunctionality (or portions of the functionality thereof) can be locatedin one or more MSO data centers, and/or in other “cloud” entities,whether within or outside of the MSO network, and distributed acrossmultiple domains (logical and hardware) as previously described.

In one embodiment, the connectivity manager 706 is further configured toregister known downstream devices (e.g., access points and nodes), otherbackend devices, and wireless client devices (remotely located orotherwise), and centrally control the broader wireless network (and anyconstituent peer-to-peer sub-networks). Such configuration include,e.g., providing network identification (e.g., to APs, client devices,background scanner, and other downstream devices, or to upstreamdevices), identifying network congestion, and managing capabilitiessupported by the wireless network.

In some embodiments, the connectivity manager 706 may also be capable ofobtaining data, and even use M2M learning or other logic to identify andlearn patterns among detected RF signals (e.g., RAT interference occursat certain times of day or locations, or how often a particular Wi-Fi APneeds to implement contention management with another RAT). Patterns maybe derived from, for example, analysis of historical data collected fromthe reports from the background scanner over time. In one variant, theconnectivity manager 706 may, without waiting for or analyzing a reportfrom the background scanner, automatically send a templatedconfiguration file to one or more APs that serve client devices that arelikely affected by contention with another RAT (e.g., LTE-U or LTE-LAA),where the templated configuration file contains typical or recurringmodifications that are made to the APs that frequently require suchmodifications.

In one embodiment, the connectivity manager 706 accesses the massstorage 705 (or the AP DB 205) to retrieve stored data. The data orinformation may relate to reports or configuration files as noted above.Such reports or files may be accessible by the connectivity manager 706and/or processor 702, as well as other network entities, e.g., a CMprovisioning server 201 or wireless APs 202, 204, 206, 208. Theconnectivity manager 706 may retrieve a configuration file from the massstorage 705, AP DB 205, or provisioning server 201, and then modifyconnectivity parameters stored in the configuration file based at leastin part on reports received from the background scanner and otheridentified network conditions (e.g., congestion level, status of APs,number of client devices), the reports containing information withrespect to, inter alia, downstream network entities and networkconditions. In one alternate variant, the CM provisioning server 201 ispart of the CC architecture (e.g., virtualized and/or incorporated as adiscrete module within the CC 210).

In other embodiments, application program interfaces (APIs) such asthose included in an MSO-provided applications, installed with otherproprietary software, or natively available on the controller apparatus(e.g., as part of the computer program noted supra or exclusivelyinternal to the connectivity manager 706) may also reside in theinternal cache or other memory 704. Such APIs may include common networkprotocols or programming languages configured to enable communicationwith other network entities as well as receipt and transmit signals thata receiving device (e.g., Wi-Fi AP, client device) may interpret.

In another embodiment, the connectivity manager 706 is furtherconfigured to communicate with one or more authentication,authorization, and accounting (AAA) servers of the network. The AAAservers are configured to provide services for, e.g., authorizationand/or control of network subscribers for controlling access andenforcing policies related thereto with respect to computer resources,enforcing policies, auditing usage, and providing the informationnecessary to bill for services. AAA servers may further be useful forproviding subscriber-exclusive features or content via, e.g.,downloadable MSO-provided applications.

In some variants, authentication processes are configured to identify anAP, a client device, or an end user, such as by having the client deviceidentify or end user enter valid credentials (e.g., user name andpassword, or Globally Unique Identifier (GUID)) before network access orother services provided by the operator may be granted to the clientdevice and its user. Following authentication, the AAA servers may grantauthorization to a subscriber user for certain features, functions,and/or tasks, including access to MSO-provided email account, cloudstorage account, streaming content, billing information, exclusive mediacontent, etc. Authentication processes may be configured to identify orestimate which of the known APs serviced by the CC 210 tend to serveusers or client devices that subscribe to the MSO's services, therebyproviding additional insights with respect to how a particular AP may betreated. For example, if a first AP serves many clients relative toanother AP, the CC may favor the first AP by, e.g., configuring theconnectivity parameters to be more aggressive, resulting in a better oradditional end-user experiences for subscribers.

Returning to the exemplary embodiment as shown in FIG. 7, one or morenetwork “front-end” interfaces 708 are utilized in the illustratedembodiment for communication with downstream network entities, e.g.,APs, background scanner, and/or other WLAN-to-controller backhaulentities and intermediate data centers, via, e.g., Ethernet or otherwired and/or wireless data network protocols. Reports transmitted fromthe background scanner are routed via the network interface to theconnectivity manager 706 within the CC protocol stack. Modifiedconfiguration files are routed via the network interface from theconnectivity manager 706 to one or more APs via inter-processcommunications (e.g., the manager 706 to a corresponding software orfirmware process running on the relevant AP).

In the exemplary embodiment, one or more backend interfaces 710 areconfigured to transact one or more network address packets with othernetworked devices, particularly backend apparatus such as the CMprovisioning server 201, CMTS, Layer 3 switch, network monitoringcenter, AAA server, etc. according to a network protocol. Commonexamples of network routing protocols include for example: InternetProtocol (IP), Internetwork Packet Exchange (IPX), and Open SystemsInterconnection (OSI) based network technologies (e.g., AsynchronousTransfer Mode (ATM), Synchronous Optical Networking (SONET), SynchronousDigital Hierarchy (SDH), Frame Relay). In one embodiment, the backendnetwork interface(s) 710 operate(s) in signal communication with thebackbone of the content delivery network (CDN), such as that of FIGS.1-2 a. These interfaces might comprise, for instance, GbE (GigabitEthernet) or other interfaces of suitable bandwidth capability.

It will also be appreciated that the two interfaces 708, 710 may beaggregated together and/or shared with other extant data interfaces,such as in cases where a controller function is virtualized withinanother component, such as an MSO network server performing thatfunction.

Scanner Apparatus—

FIG. 8 illustrates an exemplary dedicated background radio scanner 214according to the present disclosure. As shown, the background scanner214 includes, inter alia, a processor apparatus or subsystem 802, aprogram memory module 804, mass storage 805, a connectivity managerportion 806, one or more network (e.g., LAN, or backhaul) interfaces808, as well as one or more radio frequency (RF) devices 809 having,inter alia, antenna(e) 810 and one or more RF tuners 815.

Although a dedicated background scanner apparatus 214 such as that ofFIG. 8 may be used as described within the present disclosure, artisansof ordinary skill in the related arts will readily appreciate, given thepresent disclosure, that the background scanner may be virtualizedand/or distributed within other network entities (e.g., an AP, or the CC210 if locally disposed), the foregoing apparatus being purelyillustrative. In the exemplary embodiment, the processor 802 may includeone or more of a digital signal processor, microprocessor,field-programmable gate array, or plurality of processing componentsmounted on one or more substrates. The processor 802 may also comprisean internal cache memory, and is in communication with a memorysubsystem 804, which can comprise, e.g., SRAM, flash and/or SDRAMcomponents. The memory subsystem may implement one or more of DMA typehardware, so as to facilitate data accesses as is well known in the art.The memory subsystem of the exemplary embodiment containscomputer-executable instructions which are executable by the processor802.

The RF antenna(s) 810 are configured to detect signals from radio accesstechnologies (RATs) in the venue. For example, Wi-Fi signals and LTE(including, e.g., LTE-U, LTE-LAA) signals may be detected, along withnetworking information such as number and type of RATs (e.g., Wi-Fi,LTE-U, LTE-LAA), frequency bands used (e.g., 2.4 or 5.8 GHz amongothers), channels the signals are occupying, number of connections, etc.As referenced elsewhere herein, the antenna(s) 810 of the scanner mayinclude multiple spatially diverse individual elements in e.g., a MIMO-or MISO-type configuration, such that spatial diversity of the receivedsignals can be utilized. Moreover, a phased array or similar arrangementcan be used for spatial resolution within the environment, such as basedon time delays associated with signals received by respective elements.

As noted above, the scanner apparatus 214 also includes an LTE emulatormodule 813, which in the illustrated embodiment acts as receiver anddecoder of LTE-based signals. For example, in one implementation, themodule 813 includes the ability to (whether via the scanner radio 809 orits own indigenous radio) to measure RSSI and implement Zadoff-Chuautocorrelation sequence analysis for extraction of PSS timing data, aswell as logic enabling decode of one or more broadcast channels such asPDSCH or PDCCH.

The tuner 815 in one embodiment comprises a digitally controlled RFtuner capable of reception of signals via the RF front end (receivechain) of the scanner radio 809 in the aforementioned bands, includingsimultaneous reception (e.g., both 2.4 and 5.0 GHz band at the sametime), and has sufficient reception bandwidth to identify emitters thatare significantly below or above the above-listed nominal frequencies,yet still within the relevant operating band restrictions (e.g., withinthe relevant ISM band).

The processing apparatus 802 is configured to execute at least onecomputer program stored in memory 804 (e.g., a non-transitory computerreadable storage medium); in the illustrated embodiment, such programsinclude a scanner portion of the CM application 806. Other embodimentsmay implement such functionality within dedicated hardware, logic,and/or specialized co-processors (not shown).

In the illustrated embodiment, the background scanner 214 includes theconnectivity manager module portion 806. The connectivity manager 806 isa firmware or software module that collects information regarding theradio signals via the radio 809 into a report or other data structurethat is parse-able and capable of analysis by the CC 210 and/or otherupstream or backend entities.

In some embodiments, the connectivity manager program 806 utilizesmemory 804 or other storage 805 configured to temporarily hold a numberof data reports or files before transmission via the backendinterface(s) 810 to the CC 210. In other embodiments, applicationprogram interfaces (APIs) such as those included in an MSO-providedapplication or those natively available on the AP (e.g., as part of thecomputer program noted supra or associated with the connectivity manager806) may also reside in the internal cache or other memory 804. SuchAPIs may include common network protocols or programming languagesconfigured to enable communication with the CC 210 and other networkentities as well as use procedures for collecting, compressing and/orparsing information obtained via the antenna(s) 808 and radio 809 suchthat a receiving device (e.g., CC, Wi-Fi AP, etc.) may interpret thereports in order to extract and analyze the relevant information.

In a different embodiment (see dashed arrow in FIG. 8), one or morenetwork interfaces 808 are utilized for receiving communications or datafrom upstream entities such as the CC 210. In a basic implementation,the scanner is primarily just a one-way “detector” that obtains RFsignals, performs whatever processing in the digital domain it isequipped for on the signals (after conversion via the RF front end ADC),if any, and then forwards the raw or processed data to the relevantupstream entity such as the CC 210. However, in more sophisticatedimplementations, the scanner 214 may include logic to receive dataand/or commands from an upstream entity, such as e.g., configurationdata for its own radio 809 (i.e., such that the CC 210 or other upstreamentity can configure the scanner with respect to detection of theappropriate bands, MCS, energy threshold, etc.), and/or implementvarious functions such “wake/sleep”, power on/off, reset, test mode,etc. The scanner may, in certain embodiments, also be configured tocommunicate with other networked entities, including downstream andneighboring devices (e.g., Wi-Fi APs, other scanners, AP controllers)via, e.g., Ethernet or other wired and/or wireless data networkprotocols, such as via the network interface. For instance, in oneimplementation, the scanner 214 may communicate in a peer-to-peerfashion with another scanner in the venue that is not directlycontrolled by the CC 210 or other controller entity, such as toconfigure that other scanner, obtain signal data obtained thereby, oract as test beacons for each other.

Business Methods—

The foregoing examples and embodiments may be utilized for methodsdirected to furthering business operations of service providers (e.g.,cable operators).

As one example, data services provided by an MSO (e.g., cable operator)via its Wi-Fi infrastructure may be delivered to subscribers (andpotential customers) near an access point within a prescribed venue asdescribed above. By increasing the availability of Wi-Fi services usingmodified transmit parameters (e.g., lower ED threshold, increasedtransmit power and signal strength), subscribers are given more optionsfor connecting to the network (e.g., the Internet). Subscribers may feelthat the services they have subscribed to (or have utilized on a trialor incidental without being a subscriber) are highly accessible (i.e.,good network coverage), thus improving customer experience andsatisfaction, for example as compared to competing service providers.This is especially true where the service is branded by the MSO; i.e.,associated directly with the MSO as opposed to the venue. For instance,a Charter Communications-sponsored event at a venue may, as part of itsavailable services, have Wi-Fi “stuffed beacons” as previously describedherein advertising the availability of Charter Wi-Fi at the event.Non-subscriber users who have their Wi-Fi enabled can receive theinformation via the stuffed beacons (e.g., as a small pop-up ortextual/ticker notification), and enabling the notified user to merelyclick on a link to access the appropriate URL for use of the services,rather than utilize say their LTE interface. Assuming the provided WLANservices (e.g., connectivity/persistence, data rate, etc.) to becomparatively good due to better “competitiveness” with other competingRATs by virtue of e.g., reducing the ED threshold of the APs/client orother means, then user will be favorably impressed with the performancelevel and ease of connection.

Moreover, non-subscriber ad hoc users may be captured more efficientlywhen the cable operator's services (e.g., Wi-Fi connections viahotspots) are readily available. For example, in a public venue such asa waiting area or a gate at an airport, end users of mobile devices(e.g., smartphones, laptops, tablets) may seek diversion or productivityby connecting to the Internet or other wireless networks. By offering afree means of accessing such networks via Wi-Fi while conserving batterypower and data limitations (e.g., by LTE providers), users may attributean enhanced sense of satisfaction or competitive reputation with respectto the cable operator, potentially leading to a paid servicesubscription with the cable operator in the future.

Furthermore, establishments relevant at certain venues may be open tocollaboration in which network services provided, e.g., via Wi-Fi. Forinstance, a travel equipment company may seek to place advertisements infront of travelers. In this case, the cable operator may receiveconsideration for placing advertisements for the travel equipmentcompany, where end users may watch an advertisement to gain access tothe network via Wi-Fi. In one variant, existing subscribers may accessthe network without viewing an advertisement. In another variant,non-subscribers may access the network in exchange for a fee to offsetcosts of operation and/or generate revenue. Notably, the user's desireto use the WLAN service (and hence view the ads) may be directly relatedto their perceived quality of the service; i.e., data rate, ease ofconnection, persistence, etc. Most people will watch one or two shortads to obtain high-performance and reliable WLAN service, especiallywhen use of LTE (and its prospective costs) can be obviated, especiallywhen the connection to the WLAN services in a multi-RAT environment aremade easy and efficient.

It will be recognized that while certain aspects of the disclosure aredescribed in terms of a specific sequence of steps of a method, thesedescriptions are only illustrative of the broader methods of thedisclosure, and may be modified as required by the particularapplication. Certain steps may be rendered unnecessary or optional undercertain circumstances. Additionally, certain steps or functionality maybe added to the disclosed embodiments, or the order of performance oftwo or more steps permuted. All such variations are considered to beencompassed within the disclosure disclosed and claimed herein.

While the above detailed description has shown, described, and pointedout novel features of the disclosure as applied to various embodiments,it will be understood that various omissions, substitutions, and changesin the form and details of the device or process illustrated may be madeby those skilled in the art without departing from the disclosure. Thisdescription is in no way meant to be limiting, but rather should betaken as illustrative of the general principles of the disclosure. Thescope of the disclosure should be determined with reference to theclaims.

It will be further appreciated that while certain steps and aspects ofthe various methods and apparatus described herein may be performed by ahuman being, the disclosed aspects and individual methods and apparatusare generally computerized/computer-implemented. Computerized apparatusand methods are necessary to fully implement these aspects for anynumber of reasons including, without limitation, commercial viability,practicality, and even feasibility (i.e., certain steps/processes simplycannot be performed by a human being in any viable fashion).

What is claimed is:
 1. A controller apparatus for use within a managedcontent delivery network, the controller apparatus being configured tomanage wireless connectivity to a wireless-enabled device, thecontroller apparatus comprising: a processor apparatus; and a storageapparatus in data communication with the processor apparatus and havinga non-transitory computer-readable storage medium, the storage mediumcomprising at least one computer program having a plurality ofinstructions stored thereon, the plurality of instructions configuredto, when executed by the processor apparatus, cause the controllerapparatus to: detect a concurrent deployment of a first radio protocoland a second radio protocol within at least a prescribed area, thedetection being based at least on first data received from a firstnetwork apparatus downstream of the controller apparatus within themanaged content delivery network; obtain second data representative of aconfiguration of a wireless access point (AP) located within theprescribed area, the second data comprising data descriptive of aplurality of parameters associated with a wireless interface of thewireless AP utilizing the first radio protocol; modify the second datarepresentative of the configuration, the modification comprising anupdate of at least one of the plurality of parameters; and transmit themodified second data representative of the configuration to the wirelessAP, the modified second data enabling the wireless AP to modify at leastone operational characteristic associated with the wireless interfacebased on the updated at least one parameter.
 2. The controller apparatusof claim 1, wherein the modification of the at least one operationalcharacteristic comprises a change of an energy detection threshold forconnecting the wireless-enabled device to the wireless interface of thewireless AP via the first radio protocol.
 3. The controller apparatus ofclaim 1, wherein the modification of the at least one operationalcharacteristic comprises increasing a transmit power from at least oneantenna of the wireless interface of the wireless AP, the increase intransmit power of magnitude sufficient to enable the wireless-enableddevice to switch from using the second radio protocol to using the firstradio protocol.
 4. The controller apparatus of claim 1, wherein thecontroller apparatus comprises scanner apparatus configured to scanradio signals within at least the prescribed area, the scanner apparatusfurther comprising computerized logic to identify at least oneparticular type of radio access technology (RAT) based at least in parton said detection of the concurrent deployment of the second protocol.5. The controller apparatus of claim 4, wherein the detection of theconcurrent deployment of the second protocol is based at least in parton detection of at least a prescribed value of energy within one or moreprescribed frequency bands.
 6. The controller apparatus of claim 5,wherein the detection of the concurrent deployment of the secondprotocol is further based at least in part on detection of timinginformation associated with the second protocol.
 7. The controllerapparatus of claim 6, wherein the detection of the timing informationassociated with the second protocol comprises use of one or more CAZAC(constant amplitude zero autocorrelation) sequences.
 8. The controllerapparatus of claim 6, wherein the detection of the concurrent deploymentof the second protocol is further based at least in part on successfuldecode of one or more broadcast channels associated with the secondprotocol.
 9. The controller apparatus of claim 1, wherein: the pluralityof parameters comprise two or more of (i) a transmit power associatedwith the wireless AP, (ii) an energy detection threshold associated withthe wireless AP, or (iii) one or more frequencies corresponding to oneor more communication channels utilized by the wireless AP; and themodification of the at least one operational characteristic associatedwith the wireless interface is based at least on the update of the atleast one of the plurality of parameters by the controller apparatus.10. The controller apparatus of claim 1, wherein the obtained seconddata representative of the configuration of the wireless AP furthercomprises data descriptive of one or more measures of link qualityassociated with the wireless interface.
 11. The controller apparatus ofclaim 1, wherein the plurality of instructions are further configuredto, when executed by the processor apparatus, cause the controllerapparatus to obtain historical data relating to the second radioprotocol, the historical data comprising one or more measurementsassociated with interference of the deployment of the first radioprotocol by the deployment of the second radio protocol.
 12. Thecontroller apparatus of claim 11, the detection of the deployment of thesecond radio protocol being based at least in part on the one or moremeasurements being within one or more respective prescribed ranges of atleast one of (i) signal strength or power, or (ii) signal strengthrelative to interference.
 13. A networked system configured to providewireless LAN (WLAN) connectivity to at least one wireless-enabled devicelocated within a venue, the system comprising: scan apparatus configuredto: detect at least first radio frequency (RF) signals associated with afirst type of wireless technology; and configure data for transmissionto a wireless contention management process, said data comprisinginformation related to the at least first RF signals; a controllerapparatus in network data communication with the scan apparatus, thecontroller apparatus comprising the wireless contention managementprocess and configured to: receive the configured data and provide thereceived configured data to the contention management process; accessconfiguration data relating to at least one wireless access point withinthe WLAN; utilize the contention management process to modify theaccessed configuration data contained based at least on the configureddata; and transmit the modified configuration data to the at least onewireless access point, the modified configuration data enabling the atleast one wireless access point to adjust at least one connectivityparameter associated with a WLAN interface of the at least one accesspoint.
 14. The networked system of claim 13, wherein: the informationrelated to the at least first RF signals comprises information regardinga quality associated with the at least first RF signals associated withthe first type of wireless technology; and the configuration datarelating to the at least one wireless AP comprises data representativeof one or more of (i) a transmit power level, (ii) an energy detectthreshold level, or (iii) one or more beamforming parameters.
 15. Thenetworked system of claim 14, wherein controller apparatus is furtherconfigured to, based at least on the adjustment of the at least oneconnectivity parameter associated with the WLAN interface, cause areceptivity associated with the at least one wireless-enabled device tobe adjusted with respect to (i) the WLAN interface of the at least oneaccess point, and (ii) another wireless interface of at least anotheraccess point.
 16. The networked system of claim 13, wherein the scanapparatus is further configured to: detect at least second RF signalsassociated with a second type of wireless technology, the first type ofwireless technology comprising a WLAN-based communication protocol, thesecond type of wireless technology comprising a cellular-basedcommunication protocol; identify one or more statistics relating to thefirst and second type of wireless technology; and transmit theconfigured data to the controller apparatus, the configured data furthercomprising information related to the one or more statistics.
 17. Thenetworked system of claim 16, wherein the controller apparatus isfurther configured to utilize the wireless contention management processto detect the second type of wireless technology based at least on aselective decode of uplink and downlink channels present within thevenue, the selective decode comprising (i) an attempt to decode theuplink and downlink channels, and (ii) a determination that decode ofonly one of the uplink and downlink channels is successful.
 18. A methodof preferentially causing wireless LAN (WLAN) access for a multi-modemobile client device having both a WLAN interface and a cellular datainterface, and a connection management process configured to select oneof the WLAN interface and the cellular data interface, the methodcomprising: wirelessly receiving data at the client device, the receiveddata configured to enable the client device to adjust one or moreparameters associated with the WLAN interface, the adjustment configuredto compensate for operation of non-WLAN radio access technology withinan area within which the client device is then-currently located andwithin which WLAN radio access technology is operational; determining,using at least the connection management process, that the cellular datainterface is operating at a level of performance greater than a level ofperformance of the WLAN interface; based at least on the determining,adjusting the one or more parameters associated with the WLAN interfacebased at least on the received data; thereafter evaluating, using atleast the connection management process, at least one aspect of theperformance of the WLAN interface; and based at least on the evaluating,selecting the WLAN interface for data communications via the WLAN radioaccess technology.
 19. The method of claim 18, wherein: the adjusting ofthe one or more parameters associated with the WLAN interface comprisesadjusting one or more connectivity parameters such that the level ofperformance of the WLAN interface is at least approximately equivalentto the level of performance of the cellular data interface; and theselecting the WLAN interface for data communications comprises selectingthe WLAN interface in favor of the cellular data interface.
 20. Themethod of claim 18, further comprising: causing monitoring ofperformance of the data communications via the WLAN radio accesstechnology; causing identification of an insufficiency of theperformance based at least on one or more statistics associated with thedata communications via the WLAN radio access technology; and responsiveto the identification, causing additional adjustment to the one or moreparameters associated with the WLAN interface.